Overseer and Jellyseer merge

[TheTaylorLee]

With the combining of development, is their a guid on migrating from Overseer to Seer? Am I too early and need to let this cook some more?

[gauthier-th]

Nothing to do yet if you're already running Jellyseerr.
We didn't make an real announcement yet (neither updated all the docs), it will come later :)

[TheTaylorLee]

Thanks

[thedroidkid]

If were using Overseerr would it be smart to move to Jellyseerr now or wait until the merge is done? Current bug with the broken Plex Watchlist in Overseerr is killing me

[arcticfoxwp]

Super pumped about the merger!

[GrundleJuice]

If were using Overseerr would it be smart to move to Jellyseerr now or wait until the merge is done? Current bug with the broken Plex Watchlist in Overseerr is killing me

I have the same question. I am looking forward to this and the added support for lidarr/music! Thank you

[fallenbagel]

If were using Overseerr would it be smart to move to Jellyseerr now or wait until the merge is done? Current bug with the broken Plex Watchlist in Overseerr is killing me

Do not move to jellyseerr. Jellyseerr is not compatible with overseerr db. If you want the fixed watchlist api, you should be moving to seerr :develop which is designed to automatically migrate your overseerr db.

[eatonjb]

forgive my ignorance, is there a write-up, (also I am still a little new/green on docker)

I am pulling from sctx/overseerr:latest, do i somehow change it to seerr-team/seerrr:latest or something like that? or do I just sit tight for a bit. in your documentation (https://docs.seerr.dev/getting-started/docker) shows ghcr.io/fallenbagel/jellyseerr:latest, but thats not right.. as you mentioned above not to pull from jellyseerr .

[gauthier-th]

Seerr is not officially released yet. An announcement will be made once everything is completed with a migration guide for both Overseerr and Jellyseerr users.

[Clancy508]

Seerr is not officially released yet. An announcement will be made once everything is completed with a migration guide for both Overseerr and Jellyseerr users.

Would ghcr.io/fallenbagel/jellyseerr be the appropriate image to use if setting up a new system in the meantime?

[gauthier-th]

Yes. You can follow the docs: https://docs.seerr.dev/

[enoch85]

Do you have any ETA of the merge? Would it be a good idea to start using seer:develop if you plan to migrate from Overseer to Jellyseer now already?

[gauthier-th]

No ETA. You can still use Overseerr or Jellyseerr with the stable versions. Seerr is not stable yet (not released yet), but can be used as well. Just keep in mind that the develop branch is not stable, so use with caution.

[enoch85]

Changed from Overseer to Seer using the develop branch, and all good in the hood.

Thanks for your hard work!

[Superuser18]

I'm thinking of adding seerr to my arr stack and am highly confused as to which image to use!? Some help is very welcome.

[hollanbm]

If you like to test and be on the edge, then use ghcr.io/seerr-team/seerr:develop

Otherwise, fallenbagel/jellyseerr:2.7.3

Some copy-pasta for you

  jellyseerr:
    image: fallenbagel/jellyseerr:2.7.3@sha256:4538137bc5af902dece165f2bf73776d9cf4eafb6dd714670724af8f3eb77764
    init: true
    container_name: jellyseerr
    environment:
      LOG_LEVEL: debug
      TZ: America/Kentucky/Louisville
      PORT: 5055 #optional
      PUID: 1000
      PGID: 1000
    ports:
      - 5055:5055
    volumes:
      - ./Jellyseerr/config:/app/config
    healthcheck:
      test: wget --no-verbose --tries=1 --spider http://localhost:5055/api/v1/status || exit 1
      start_period: 20s
      timeout: 3s
      interval: 15s
      retries: 3
    restart: unless-stopped

[Superuser18]

Thanks a lot. I went with the seerr:develop image as i like to live on the edge ;)

[hammamboumou]

I saw in the migration guide that node user with 1000 UID/GID is goins to be used and that user directive is to be removed. I don't think this approach is the right one, considering a setup with specific UID/GID for each service, there should be a way to set a specific UID/GID for the user running the seer instance. What are your thoughts on this?

[DuvelCorp]

Agreed. Its bad docker practice to not specify a user for the container and let it run with root permissions.

[bannert1337]

I'd like to respectfully ask for some clarity on the release timeline and what's actually blocking a stable Seerr release.
It's been over 5 months since the last release (v2.7.3 on August 14, 2025), and I'm having trouble reconciling these statements:

1. "No major updates will be merged for our first release" (from the OIDC discussion)
2. "Seerr is not stable yet"
3. Jellyseerr v2.7.3 is already stable and supports Jellyfin, Plex, and Emby

If the first Seerr release is essentially Jellyseerr rebranded with Overseerr migration support — and no major new features — what's preventing a stable release? The core functionality has been production-ready for years.
Meanwhile, there are tested PRs for highly requested features (OIDC, music support, etc.) sitting in limbo because they won't be merged until after a first release that has no ETA.
I understand this is a volunteer project and I appreciate the work that goes into it. But the current situation leaves users in an awkward spot: told to use develop for testing, but also told it's "not stable," while the stable Jellyseerr releases are effectively EOL.
Could the maintainers provide:

• What specific blockers remain before a stable release?
• A rough timeline, even if it's "Q1 2026" or "when X is done"?
• Or at minimum, acknowledgment if this is a bandwidth/capacity issue so the community can set expectations accordingly?

Thanks for your work on this project.

[gauthier-th]

I'm not going to explain all this one more time. Please read this answer for more explanation.

Our community lives on Discord, not GitHub, you can go there to read the announcements and some of our answers for more details.

And finally, we are all contributors who give our free time to this project. We all have jobs and lives outside of this. Expecting fixed and precise timelines is unreasonable when we are already doing everything we can.

[enoch85]

All the people who hit the dislike button here: Have you contributed to the project..?

Try to be thankful for what other people are doing on their spare time, for free.

[johnistheman]

To be clear, my thumbs down was not for the work being done - that is very much appreciated.

I also don't love the tone the OP (bannert1337) used here. It's a bit entitled sounding IMO - look, people do this for free, that means demands are a bit crazy and tone matters a lot.

And finally, we are all contributors who give our free time to this project. We all have jobs and lives outside of this. Expecting fixed and precise timelines is unreasonable when we are already doing everything we can.

For example, this I agree with 100%.

My thumbs down was for:

Our community lives on Discord, not GitHub, you can go there to read the announcements and some of our answers for more details.

It makes complete sense that developers and contributors to the project may want to communicate with each other via Discord. It's not so public, it's real-time, ephemeral, etc.

For those exact reasons though, Discord is a not a good place to communicate with the vast majority of the people that use the project. Discord is not the public internet, it's not indexed, and it's not easily searchable. Having to go there to get up to date information doesn't make much sense. I'm even in the Discord and I have no idea where to find the "announcements and answers" gauthier-th is referring to.

Having said that, the contributors to the project are free to handle this however they want - like I said, it's their time and effort, and it's appreciated.

To be clear, my thumbs down was not for the work being done - that is very much appreciated.

I also don't love the tone the OP (bannert1337) used here. It's a bit entitled sounding IMO - look, people do this for free, that means demands are a bit crazy and tone matters a lot.

And finally, we are all contributors who give our free time to this project. We all have jobs and lives outside of this. Expecting fixed and precise timelines is unreasonable when we are already doing everything we can.

For example, this I agree with 100%.

My thumbs down was for:

Our community lives on Discord, not GitHub, you can go there to read the announcements and some of our answers for more details.

It makes complete sense that developers and contributors to the project may want to communicate with each other via Discord. It's not so public, it's real-time, ephemeral, etc.

For those exact reasons though, Discord is a not a good place to communicate with the vast majority of the people that use the project. Discord is not the public internet, it's not indexed, and it's not easily searchable. Having to go there to get up to date information doesn't make much sense. I'm even in the Discord and I have no idea where to find the "announcements and answers" gauthier-th is referring to.

Having said that, the contributors to the project are free to handle this however they want - like I said, it's their time and effort, and it's appreciated.

We have time and time again mentioned in many discussions even on github that we are all volunteers working on a free time who all have full-time jobs/full-time students. We are not a company. We are not an organisation. We just provide a free software that is open-source, to anyone who likes to use it. In our free-time. So we cannot provide an ETA. We do not have a set timeline.

If you are unsure any work is going on, you can look at our github history and PRs that open that references seerr and you can clearly see the merge process is still ongoing which includes fixing bugs that were present in both overseerr and jellyseerr to ensure that seerr first release as stable as it can be and updating documentation everywhere. This is all public information available in a public location.

[mattsigal]

With today's 3.0 release are we getting closer to the recommended merge?

[fallenbagel]

Merge of what?

[DrMcCoy]

Oh, neat, this seems to be a friendly merger? Congratz, thats nice to see

There's still a lot of "Jellyseerr" in the HTML sources, though. Even visible, in the title tags, for example

[fallenbagel]

Could you link where? If those places are i18n translated places then it should be handled in weblate

[DrMcCoy]

Oh, I haven't actually seen where it's in the source source, just saw that my browser's tab still says "Jellyseerr" (yes, even with clearing the cache), and looking at the HTML in the browser, there's:

It is the current version 3.0.1, and it is in English, too:

I don't actually know where this is coming from, though.

[DrMcCoy]

Oooh, duh. Seems like that comes from the Settings and is a text you can enter.

Nevermind, my bad, sorry

[ClassicUA]

Hi. Need help.
Jellyseerr was running on Synology with the following docker compose

services:
  jellyseerr:
    image: fallenbagel/jellyseerr:latest
    container_name: Jellyseerr
    ports:
    - 5056:5055
    security_opt:
      - no-new-privileges:false
    volumes:
      - /volume1/docker/jellyseerr:/app/config:rw
    environment:
      TZ: Europe/Bucharest
      PUID: 1026
      PGID: 100
    restart: on-failure:5

Replaced the image with ghcr.io/seerr-team/seerr:latest and started getting an error

Node.js v22.22.0

> seerr@3.0.1 start

> NODE_ENV=production node dist/index.js

2026-02-15T00:45:39.547Z [info]: Commit Tag: 789bcc8eec3414da373328e374c2edb1abc3ac0d 

2026-02-15T00:45:40.442Z [info]: Starting Seerr version 3.0.1 

node:events:497

      throw er; // Unhandled ‘error’ event

      ^

Error: EACCES: permission denied, open '/app/config/logs/seerr-2026-02-15.log'

Emitted ‘error’ event at:

    at WriteStream.<anonymous> (/app/node_modules/.pnpm/file-stream-rotator@0.6.1/node_modules/file-stream-rotator/FileStreamRotator.js:697:15)

    at WriteStream.emit (node:events:519:28)

    at emitErrorNT (node:internal/streams/destroy:170:8)

    at emitErrorCloseNT (node:internal/streams/destroy:129:3)

    at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {

  errno: -13,

  code: ‘EACCES’,

  syscall: ‘open’,

  path: ‘/app/config/logs/seerr-2026-02-15.log’

}

[hollanbm]

1. Stop the container
2. Fix the permissions
3. Delete the contents of your logs folder
4. Start the container

[ClassicUA]

How exactly do you change permissions? And why does jellyseerr work fine, but seerr complains about permissions?

[hollanbm]

How exactly do you change permissions? And why does jellyseerr work fine, but seerr complains about permissions?

Seerr now runs as node user id 1000, your previous container probably ran as root.

seerr/docs/migration-guide.mdx

Line 54 in c2977f6

Since the container now runs as the `node` user (UID 1000), you must ensure your config folder has the correct permissions. The `node` user must have read and write access to the `/app/config` directory.

Change the ownership on the files to chown -R 1000:1000 /path/to/seerr/config

[ClassicUA]

How exactly do you change permissions? And why does jellyseerr work fine, but seerr complains about permissions?

Seerr now runs as node user id 1000, your previous container probably ran as root.

seerr/docs/migration-guide.mdx

Line 54 in c2977f6

Since the container now runs as the `node` user (UID 1000), you must ensure your config folder has the correct permissions. The `node` user must have read and write access to the `/app/config` directory.

Change the ownership on the files to chown -R 1000:1000 /path/to/seerr/config

Now it works, thank you.

[ridizy]

You can try changing the end of your compose file to the below. Moving the user/group info to the user: option.

    volumes:
      - /volume1/docker/jellyseerr:/app/config:rw
    user: 1026:100
    environment:
      TZ: Europe/Bucharest
    restart: on-failure:5

[hollanbm]

You can try changing the end of your compose file to the below. Moving the user/group info to the user: option.

    volumes:
      - /volume1/docker/jellyseerr:/app/config:rw
    user: 1026:100
    environment:
      TZ: Europe/Bucharest
    restart: on-failure:5

That won't change the ownership of the previous files, just the user seerr runs as

[ridizy]

Good point. Either change the user it runs as or the file owner. Not both.

[Superuser18]

Did you guys even read the migration guide?