Skip to content
This repository was archived by the owner on Feb 15, 2026. It is now read-only.
This repository was archived by the owner on Feb 15, 2026. It is now read-only.

User tags fail to create in Radarr due to invalid characters (spaces) #4321

Description

@DEADSEC-SECURITY

Description

When a user makes a movie request through Overseerr, the auto-generated user tag fails to create in Radarr with a 400 error. This is because Overseerr generates tags in the format {userId} - {username} (e.g., 9 - celesbuffard), which includes spaces.

Recent versions of Radarr have tightened tag validation to only allow lowercase a-z, 0-9, and - characters. Spaces are no longer permitted.

Expected Behavior:
User tag is created successfully in Radarr.

Actual Behavior:
Tag creation fails with HTTP 400. The movie request itself succeeds, but per-user tracking via tags does not work.

Environment:
Overseerr version: 1.34.0
Radarr version: 6.0.4.10291
Installation: Docker

Suggested Fix:
Sanitize the generated tag to replace spaces with hyphens and ensure only valid characters are used. For example, 9 - celesbuffard should become 9-celesbuffard.

Version

1.34.0

Steps to Reproduce

  1. Configure Overseerr with Radarr integration and enable user tags
  2. Have a user submit a movie request
  3. Observe tag creation failure in logs

Screenshots

No response

Logs

Overseerr:

[error][Media Request]: Something went wrong sending request to Radarr {"errorMessage":"[Radarr] Failed to create tag: Request failed with status code 400","requestId":636,"mediaId":1234}


Radarr:

[Warn] RadarrErrorPipeline: Invalid request Validation failed: 
 -- Label: Allowed characters a-z, 0-9 and -

Platform

desktop

Device

Docker

Operating System

Docker

Browser

Any

Additional Context

No response

Code of Conduct

  • I agree to follow Overseerr's Code of Conduct

Activity

  1. Unijens commented on Jan 11, 2026

    @Unijens

    Also just stumpled upon this issue with same error code.
    Radarr version: 6.0.4.10291
    Overseerr version: 1.34.0
    Also running in docker

  2. bcole commented on Jan 12, 2026

    @bcole

    +1 on this issue. I've got the latest versions as well:
    Radarr version: 6.0.4.10291
    Overseerr: 1.34.0

    Any workarounds for short-term? Should I try to downgrade Radarr for now?

  3. hollowpnt92 commented on Jan 14, 2026

    @hollowpnt92

    +1 on this issue

  4. YellerFeller commented on Jan 16, 2026

    @YellerFeller

    +1 on this

  5. engelbrechtd commented on Jan 18, 2026

    @engelbrechtd

    +1

    1. Overseerr Version: 1.34.0
    2. Radarr Version: 6.1.1.10317
  6. lunchpot commented on Jan 19, 2026

    @lunchpot

    +1 on this issue. I've got the latest versions as well: Radarr version: 6.0.4.10291 Overseerr: 1.34.0

    Any workarounds for short-term? Should I try to downgrade Radarr for now?

    The workaround for me at the moment is to disable tagging within Overseer for now.

    Settings > Services > Radarr > Tag Requests [uncheck]

  7. bcole commented on Jan 20, 2026

    @bcole

    The workaround for me at the moment is to disable tagging within Overseer for now.

    Thanks, but this workaround prevents things like user specific Plex lists in agregarr etc, so I wouldn't recommend this if you use these features (I do).

    An alternate workaround I'm using is downgrading Radarr for now, e.g.:

    lscr.io/linuxserver/radarr:5.28.0
    

    This is non-ideal either but at least allows user sign up for now.

    I'll follow this thread to see if there is a proper fix in works, thanks!

  8. minermartijn commented on Jan 28, 2026

    @minermartijn

    Im using the hotio containers, do you know which version i need to set this to then?
    Because im not sure which is version 5.28 so i can use the correct tags again. I need them

  9. mitchscobell commented on Feb 5, 2026

    @mitchscobell

    Following this too, causing issues for me. I won't be able to switch off of my other request app, because I want to see with simple tags of who requested them. I don't really need the userId at all for that. It's using {userId} - {username}, it'd be great to have that a configurable format to things like {userId} - {username} or {userId}-{username} or {username}.

    Like how Radarr has this:

    Image
  10. added a commit that references this issue on Feb 5, 2026
    cef7edc
  11. dspaan commented on Feb 10, 2026

    @dspaan

    This is a duplicatie issue from this and this. In issue 4306 people mention an announcement that Overseerr is and Jellyseerr are being merged, see here: https://github.com/seerr-team/seerr?tab=readme-ov-file

    Unfortunately it's still in beta but you can try it at your own risk, it looks like the autotags problem is already fix in the dev version though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions