sct
Possibly illegal Tags for Sonarr/Radarr
Description
According to https://github.com/Sonarr/Sonarr/issues/7796 allowing spaces in tags passed to the API might be a bug, and depending on this issue might be banned.
Version
1.34.0
Steps to Reproduce
- Enable movie/series tagging for Radarr/Sonarr
- Request a movie/series
- Notice a tag in the form of
1 - Andyappears in Radarr/Sonarr
Platform
desktop
Operating System
Linux (docker)
Browser
Chrome
Additional Context
As some tools, such as Bazarr also validate tags via the regex in an effort to stay aligned with Sonarr/Radarr, the tags generated by Overseerr are currently unusable for such tools
Possible solutions:
1 . Allow a custom tag format, even if it's buried in a config file (this would be preferred)
2. Swap spaces to -s
Code of Conduct
- [x] I agree to follow Overseerr's Code of Conduct
It might be worth being proactive here- even if this ends up being permitted in the end, so that if they patch the API to disallow spaces, it doesn't start throwing errors on every new request.
Can confirm both radarr and sonarr will no longer accept non-conforming tags from overseerr with spaces. This must be a recent enforcement as I have had previous tags allowed. There is some fallback to existing tags happening, so I've had users being notified of requests they didnt make. Other times it gives an error, the tag cant be created and the request doesnt go through. Hangs in some pending limbo land. The spaces have got to go. Thank you in advance :-)
{ "propertyName": "Label", "errorMessage": "Allowed characters a-z, 0-9 and -", "attemptedValue": "2 - john.au", "severity": "error", "errorCode": "RegularExpressionValidator", "formattedMessageArguments": [], "formattedMessagePlaceholderValues": { "regularExpression": "^[a-z0-9-]\u002B$", "propertyName": "Label", "propertyValue": "2 - john.au" } }
In the upcoming Radarr v6 it seems the API will validate tags. From their develop branch: https://github.com/Radarr/Radarr/commit/62a05e2765ee603fa1a48806f1f20ccc936d8b8c
Jellseerr just patched this: https://github.com/fallenbagel/jellyseerr/pull/1913
Radarr Version: 6.0.3.10276 Overseerr: 1.34.0
Encountered this issue just now, overseerr log:
2025-11-14T11:30:52.248Z [info][Media Request]: Requester has no active tag. Creating new{"mediaId":1860,"newTag":"8 - hypie","requestId":444,"userId":8}
2025-11-14T11:30:52.255Z [error][Media Request]: Something went wrong sending request to Radarr{"errorMessage":"[Radarr] Failed to create tag: Request failed with status code 400","mediaId":1860,"requestId":444}
and in radarr:
Invalid request Validation failed: -- Label: Allowed characters a-z, 0-9 and -
Requests by existing users who have tags with spaces still succeed though.
Soon after i commented here the announcement came out that overseerr was merging with jellyseerr into seerr. So for anyone having this issue it’s time to make the switch. You can just swap to the seerr preview image and use the same overseerr or jellyseerr db they both worked for me. Tags work fine now so long as your plex or jellyfin username doesnt contain any illegal characters.
@Jandalslap Stupid question here. How do I swap to the seerr preview image? I'm using sctx/overseerr:latest in my compose file now.
@sleighton use this image in your compose instead. Take a backup of your config folder first just in case :-)
fallenbagel/jellyseerr:preview-seerr
@Jandalslap Stupid question here. How do I swap to the seerr preview image? I'm using sctx/overseerr:latest in my compose file now.
Be careful about doing this. The databases are not (or at least were not) inter-compatible. There are conversions scripts. If you are using the develop script it is possible this conversion might be automatic if the db is detected as overseerr, but you should double check this and backup your data before doing so
For those who want to migrate: https://github.com/pixelhunterX/seerr-database-migration/tree/master The rules might be different for the develop branch though.
@zwimer It appears to be a drop in replacement as far as I can tell. I logged into the UI and all of my stuff was there. The log indicated that it had migrated a bunch of stuff so it probably is not backward compatible (I saved my overseerr setup separately so I can fire it up to go backwards if need be).
The only things I noticed that may be a concern are 1) a user requested a movie and series when I switched over, it sent those to radarr and Sonarr and both were picked up and downloaded and now appear in Plex but neither one has updated in Seerr, they still show 'requested' and it's been 30 minutes or so, and 2) I am still getting the 401 errors in the log
025-11-14T22:50:01.485Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 401"}
I was hoping those would go away. I get a ton of them but the watchlist seems to be working just fine.
That rings a bell actually. I think i removed existing requests not available and re-requested them and they worked fine from there.
@Jandalslap Well false alarm. They just showed up it apparently just took longer than I expected. Both are now in recently added in Seerr and marked available or partially available.
@sleighton oh that’s cool then. I think my issue was actually related to my homepage widget where they wouldn’t show up as available or come off pending. Something like that. Sorry I’m struggling to remember now it was a couple months ago :)