Users unable to request series but able to request Movies - despite permissions being set

[severe junco]

As per title, users are unable to request series - the radio button is greyed out despite their permissions being set correctly. See attached photos. I can pull logs as well but not sure which ones are pertinent and also not sure how to extract them from the docker container.

[cedar pier]

Is this enabled in Settings > General ?

[barren ice]

Also need more information on your setup

Is this jellyserr?

Overseerr?

Overseerr -> jellyseerr migrated?

Seerr?

[severe junco]

Yessir

[severe junco]

Seerr, the dev branch. Migrated from overseerr. Running in a docker

[barren ice]

Tell me the steps you did to migrate

And show me your compose

Because this usually happens when the perms are fucked due to a bad migration

[severe junco]

I copied the database over into the docker and then composed it, I had to change some variable before it worked. I will note that users have successfully requested stuff before, its an odd issue

[barren ice]

Compose please

[severe junco]

'services:

jellyseerr:

image: ghcr.io/seerr-team/seerr:develop init: true

container_name: jellyseerr

environment:

LOG_LEVEL=debug

TZ=Asia/Tashkent

PORT=5055 #optional

ports:

5055:5055

volumes:

• /opt/overseerr:/app/config

healthcheck:

test: wget --no-verbose --tries=1

start_period: 20s

timeout: 3s

interval: 15s

retries: 3

restart: unless-stopped'

[barren ice]

And logs

[severe junco]

Which ones and how do I get them? Sorry I'm not great with dockers

[barren ice]

Okay first keep the logs for later but try making a test new local user or try with another user to request

See if its greyed out

Bc if it is, its a corrupted user perm

Also for logs you go to /opt/overseerr/config and logs folder and send seerr.log

[severe junco]

I've had another user have this issue before, and I fixed it somehow by removing and re-adding their permissions (or something like that, I don't remember because I just did everything I could think of and eventually it worked)

[barren ice]

Where is this perms screenshot from

Users > edit user?

Or settings > users

[severe junco]

Editing a user yes

Trying to work out how to get the log file via ssh lol

[barren ice]

Go to bulk edit and remove requsst entirely from that user

Tjen see what they see when they try to rrquesy

[barren ice]

Sounds like for some reason your db is not good

[severe junco]

Okay I'll have to give a go in a little while as I need to head out but I'll report back shortly

[barren ice]

I might be asleep since I havent slept in days. If so CC: @cedar pier

[severe junco]

Okay so bulk edit did naff all

[cedar pier]

"naff" ? 🤔

[severe junco]

Oh sorry, a Britishism, it didn't do anything 🤣

[cedar pier]

Ooh British slang I see !

Did you manage to get the logs ?

[severe junco]

I think this is it? I run it on a headless server so I have to fight with sftp for everything like that

[cedar pier]

Logs don't tell much
Have you tried creating a local user and request ?

[severe junco]

No sorry let me try that

I can't seem to login with a local user

[cedar pier]

To login with a local user you must use the email, not the username

[severe junco]

ah crikey, let me try again sorry

yeah, the test user works fine

[severe junco]

@barren ice sorry to tag you, do you know how I might be able to fix it?

[barren ice]

Are you comfortable with editting db?

Lets edit db and fix the perms

[severe junco]

I don't have a clue how to do that, can I do it with a text editor?

[barren ice]

Take a backup of your db first. Stop seerr. Then we can edit

[severe junco]

like nano?

[barren ice]

No

So there are two ways

If you have access to a gui

For example windows or sth you can use sqlite browser

So you can edit like an excel sheet

If not we can use sqlite3 package in terminal

[severe junco]

I can probably SFTP the file from the remote system and then replace it afterwards

[barren ice]

Choose which method you want and I can dictate how to fix

[severe junco]

yeah let me copy it from the remote system and then I can edit it on my windows workstation, I think I have some sort of database editing software on here

where does it live?

[barren ice]

Wherever you mounted your config folder

[severe junco]

okay so I guess that's opt then

[barren ice]

You can use https://tableplus.com/ too. Very simple to use. Trial version works

Or sqlitebrowser too

[barren ice]

/opt/config

[severe junco]

I think I have it

[barren ice]

Okay ping me when you have the db opened

[severe junco]

I think I have

does this look right?

[barren ice]

Yws now open user

Table

[severe junco]

yep

[barren ice]

Find that affected user's record

And show me their permission vs someone's else that can request their perms

[severe junco]

where are their permissions?

[barren ice]

Its a column

[severe junco]

this is what I can see

never mind

2 is the admin user, the rest are all 32

[barren ice]

Hmm. Is the affected user also 32?...

[severe junco]

yes

[barren ice]

Okay i have another thing i wanna check

[severe junco]

this is all of my users, in fact

[barren ice]

On the working user, did you try to request the same series?

[severe junco]

I have had this issue before with another user, and I just ended up requesting the series as the admin user and it worked fine

[barren ice]

Do not request as the amdin

For this specific series

I think i have an idea whats happening

[barren ice]

So please check this

[severe junco]

it's any user and any series, but when I tried the same series with the local test user I made, it worked fine

[barren ice]

No users are able to request anything?

[severe junco]

let me see if I can get a specific user to request a specific series and I will try with the test user

[severe junco]

it's odd, it's almost like the error comes and goes as it pleases. I thought it was a user error until I've had numerous users on different ISPs/browsers etc report hte same thing

[barren ice]

Wait

Wait

[severe junco]

bear with me I am just getting one of my users to try a series

[barren ice]

These perms looks wrong

I just checked mine

202375200

74448928

[severe junco]

right so update from my test user and my user user, they tried requesting this series:

and the system didn't allow it, can't move the radio buttons whatever

Local TestUser successfully requested it

[barren ice]

Can you set

The broken user's perms

To

202375200

[severe junco]

instead of 32?

[barren ice]

Because your perms on your db and mine doesnt match

At all

Yeah

The only one that matches is your admin user

[severe junco]

I suspect it's some sort of overseerr/seerr database weirdness, but that wouldn't explain why the new test user I made yesterday also has the same perms

[severe junco]

let me try sure

[barren ice]

No. More like your migration might have fucked up. Because I have overseerr db -> also showing proper perms. This couldve happened if you accidentally went from overseerr -> jellyseerr instead of seerr then changed to develop tag. Because then the migrations would not run

Because thats exactly what happened to everyone else who had the same issue as you

(I have provided support for around 5 people that had that happen)

[severe junco]

I don't think I did that, but it wouldn't surprise me at all

lol

okay, just copying the edited DB back to teh server and re-running the docker now

I just need to wait for my user to check and see if the changed permission has worked

[barren ice]

Nvm

I just saw you wrote you use docker

[severe junco]

I do use docker, but I'm mounting my old database from when it was a snap package

[barren ice]

This could also be why

[severe junco]

which I copied somewhere

[barren ice]

Snap package is EXTREMELY

Outdated

[severe junco]

oh yeah that's why I moved to the develop branch on seerr

[barren ice]

We only wrote migration to be compativle from latest ovverseerr -> seerr

Its very likely its not at all compatible from snap package overseerr -> seerr

[severe junco]

so that would be totally unsurprising if the migration shat itself

I mean it mostly seemed to work fine

[barren ice]

Thing is overseerr also introduced several perms after snap package. Each perm is treated like in layman terms a number assigned. But for some reason your perms seem to be broken. Or something else is broken. During the migration. Because I do see 32 perm = request but it could be somehow affecting. The only other thing I can think of if the edited db still failed is to try this. Stop seerr. Backup settings.json. delete it. And restart. Go through the setup page. See if they can still request to see if it was settings.json that messed up during migration and partial request is not working. But its very likely the snap package db -> seerr migration is whats causing this unintended behaviour

[severe junco]

I'm just waiting for my user to try with the modified permissions, otherwise I will re-run setup 🙂

[barren ice]

The setup rerun wont remove your db bte

Its just a regeneration of settings.json

[severe junco]

yeah I know, I had to do it before for something else

[barren ice]

Was it because you got an error saying

"Apikey" something something?

Because if so

That confirms it

[severe junco]

yes

I just trudged through my past messages

[barren ice]

As during the migration from overseerr you wouldnt need to generate settings.json and only would need if like the incompatibility thing happened (whether overseerr snap -> seerr or accidentally overserrr -> jellyseerr)

[severe junco]

#development message

[barren ice]

Yeah

#development message

That only happens if you accidentally switch to jellyseerr first 😅

That breaks perms

So far everyone who did that

[severe junco]

nuts 🤣

[barren ice]

Had this exact issue

[severe junco]

what's the resolution? changing the user's perms didn't fix it it seems

[barren ice]

Hmm. Something else must have not migrated either and thats the issue

Would need to proper dive into your db to see what the inconsistency is coming from

Another thing would be

CC: @blazing perch would they be able to retrigger all the typeorm migrations to fix the issue?

[severe junco]

I don't mind sharing it, I assume all of the passwords etc are hashed anyway

[barren ice]

They are but lets see if we can retrigger migrations first

I am not that familiar with that

Gauthier have dealt with something like this before

Incompatible migrations

He might know

Lets wait for an answer from him

[blazing perch]

can you summarize the issue?

it's just a db migration that didn't run?

[severe junco]

I migrated from a very old snap install of Overseerr, and I've messed it up somehow so that I have a weird intermittent problem with users being unable to request TV series (but seemingly always able to make movie requests)

[barren ice]

So the issue is

You know how when you migrate from overseerr -> jellyseerr instead of seerr you have to end up deleting settings.json because migrations didnt run. And that also breaks database where everyone who had that happen had their users perms all fucked up that they can no longer request? (I linked you to all the occurrences of it before but I can if needed).

This user also has the exact same issue happening but they mentioned they didnt migrate to jellyseerr but they had the same settings.json issue and they migrated from very old overseerr db. But I still feel like there was an accidental jellyseerr run due to the error they pasted earlier which cannot happen on seerr. But we are all past that now. The issue is now the seerr migrations were probably skipped. Is there a way for them to retrigger it?

Overseerr -> seerr migration

[blazing perch]

this migration is triggered when there is no mediaServerType in the settings.json

stop your instance, remove the line with mediaServerType in your settings.json, and start it again

you should see the migration happenign

(which should re-run all the jellyseerr migrations)

[severe junco]

let me try that now

I get the following error:

[blazing perch]

did you try that on the old overseerr db?

if you accidentally run a jellyseerr instance on that db, some migrations may have been already ran (like the blacklist one), so if possible the best way would be to start from your old overseerr db and run this again

[severe junco]

it was the most recent DB, the one I was using beforfe

I didn't change anything other than deleting that line in the settings json

I don't think I still have the orignal DB either

is it easier to just delete the database entirely and start again? I'm not too precious about keeping a record of my past requests to be honest, I would rather have it work and all of my users are imported from plex in any case

[barren ice]

Then yes. Would be the best fix than playing whack-a-mole with the db migrations 😅

You can stop seerr, take a backup of your current db in config/db folder and delete both the db and the settings.json

[severe junco]

right I'm just going to nuke it then 🤣 when I recreate the docker will it generate a new one?

[barren ice]

You need to reset the config folder

[severe junco]

great, I will do that

[barren ice]

Lmk how it goes!

[severe junco]

yeah, it appears to have worked. I am just re-adding all of my notifications etc!

[blazing perch]

you can replace your settings.json with the old one you had

so that you don't have to setup this again

[severe junco]

oh I've already done it now, didn't take long

it's only a webhook and a the SMTP server

[blazing perch]

all good then :)

[barren ice]

Also little tip