Getting error when an user request a media

[storm solar]

Hello,
i have some users on my overseer and everything has always worked fine.
Since yesterday, however, I added a couple of new users, but when they request media, it's not sent to radarr.
I checked the logs and it gives me this error:

2025-12-29T09:45:27.074Z [debug][Notifications]: Sending Discord notification {"type":"MEDIA_AUTO_APPROVED","subject":"Ghosted (2023)"}
2025-12-29T09:45:27.081Z [debug][Notifications]: Sending Telegram notification {"type":"MEDIA_AUTO_APPROVED","subject":"Ghosted (2023)"}
2025-12-29T09:45:27.085Z [debug][Notifications]: Sending webhook notification {"type":"MEDIA_AUTO_APPROVED","subject":"Ghosted (2023)"}
2025-12-29T09:45:27.956Z [info][Media Request]: Requester has no active tag. Creating new {"requestId":139,"mediaId":660,"userId":9,"newTag":"9 - danielf973"}
2025-12-29T09:45:29.016Z [error][Media Request]: Something went wrong sending request to Radarr {"errorMessage":"[Radarr] Failed to create tag: Request failed with status code 400","requestId":139,"mediaId":660}```

How do I fix it? 

Thanks

[grim lava]

Go to settings > services > radarr

And turn off tag requests

[storm solar]

But i need tags. Because i use tags to delete media after some days with maintaineer

It's also useful for me to understand who requested that media from radarr/sonarr.
Anyway, it's always worked with other users so far! Why doesn't it work now?

[grim lava]

Until next version you need yo disable it.

[grim lava]

Because those users tags already exist. Only used that doesnt have. Cannot be created anymore. Bc radarr diesnt alloe spaces in tags anymore.

And the fix for that will be available in seerr's release.

You can use seerr develop. But thats for beta testing and make sure to take a backup and everything.

[storm solar]

Can’t I create a tag manually in radarr with same of overseer and let it work?

[grim lava]

radarr doesnt allow spaces in names anymore

[storm solar]

Uhmmm...so can't have media tagged until seerr became stable?

[grim lava]

Or just use develop. But yeah the fix is not available in overseerr

[storm solar]

But if I install the Seerr release, do I have to reset everything from scratch?
But will I have to do it again when the final version of Seerr is released?

[grim lava]

No

Thats the whole point of the merger. It will automatically migrate your db.

[storm solar]

Oh great, si there a guide to follow?

So tags then will work normally?

[grim lava]

Yes

[grim lava]

Migration guide will be posted when it releases. If you want to beta test you can check description of #seerr-beta and use the develop tag

[storm solar]

But also with the beta can I migrate all my db from my actual overseerr?

[grim lava]

Beta is still seerr.

Its just not released. Its the same thing. So ofc? Check #announcements

[storm solar]

ofc means?

[storm solar]

I've already looked in announcements and found the string to install the beta (fallenbagel/jellyseerr:preview-seerr).

I'd like to know:

1. If I install this beta, will the tags work correctly for new users?
2. What do I need to do to install it while keeping the old database?

[grim lava]

Dont use that tag

Use the on in migration guide

[storm solar]

I mean, the radarr tags. Will the overseerr beta fix the radarr tags that are currently giving me problems for new users?

[grim lava]

1. yes if your users dont have this format names "John Doe" and only has "John". If they do have spaces in their username then wait for this pr https://github.com/seerr-team/seerr/pull/2231 which once merged develop tag will be updated immediately

2. please read the migration guide in #seerr-beta

[grim lava]

There is no overseerr beta.

[storm solar]

Yes sorry, seer beta I mean

No my users don't have spaces

Could you please link me the migration guide? Is there in that chanell as message?

Or if you want you can explain me here

I am on synology using docker compose

This is my actual compose:

    container_name: overseerr
    hostname: overseerr
    image: ghcr.io/hotio/overseerr
    restart: unless-stopped
    logging:
      driver: json-file
      options:
        max-file: ${DOCKERLOGGING_MAXFILE}
        max-size: ${DOCKERLOGGING_MAXSIZE}
    labels:
      - org.hotio.pullio.update=${PULLIO_UPDATE}
      - org.hotio.pullio.notify=${PULLIO_NOTIFY}
      - org.hotio.pullio.discord.webhook=${PULLIO_DISCORD_WEBHOOK}
    ports:
      - 5055:5055
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - ${DOCKERCONFDIR}/overseerr:/config
      - ${DOCKERSTORAGEDIR}/libreria:/media/libreria
      ```

[storm solar]

Ok i am reading the migration guide

First have to rename my "overseerr" folder in "seer", right?

Guide says "all references"...What else besides the folder?

[grim lava]

Its in the channel description

[storm solar]

Yes found it

[grim lava]

Change the image. Servie name. Container name. Hostname

[storm solar]

kmagw what is?

[grim lava]

Sorry haha editted

I am walking rn 😅

[storm solar]

I done that:

1. renamed the config folder from "overseerr" to "seerr"
2. stopped overseerr container
3. commented all old overseerr compose in my docker-compose
4. pasted the new seerr compose taked from migration guide
5. pulled a runned seerr

Is that ok?

My new compose is now:

    image: ghcr.io/seerr-team/seerr:develop
    init: true
    container_name: seerr
    environment:
      - LOG_LEVEL=debug
      - TZ=${TZ}
      - PORT=5055 #optional
    ports:
      - 5055:5055
    volumes:
      - ${DOCKERCONFDIR}/seerr:/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
    labels:
      - org.hotio.pullio.update=${PULLIO_UPDATE}
      - org.hotio.pullio.notify=${PULLIO_NOTIFY}
      - org.hotio.pullio.discord.webhook=${PULLIO_DISCORD_WEBHOOK}```

In the "image" I have changed the final "latest" with "develop", right?

[grim lava]

Also make sure to set the correct permisison for the config folder as said in the migration guide

[storm solar]

I had my own dedicated "docker" user for all containers but it can't work with this one?

So i changed the seerr folder permission to 1000:1000

[grim lava]

Yeah thats fine too

[storm solar]

Correct to change latest with develop?

The migration guide says "latest" in the compose

[grim lava]

Thats for seerr release

Youre trying to beta test so yes

[storm solar]

Ok, now all seems work correctly

Tried adding from user and works

Is normal i see "jellyseerr" logo?

[grim lava]

Yes

[storm solar]

Ok, and when official seerr will be released what I have to do?

[grim lava]

Just change develop to latest

[storm solar]

Ok great