Getting `Oops` Error when trying to view some profiles | Seerr | Page 1

lone sage Feb 14, 2026, 10:59 PM

#

Just migrated from Overseer to Seer 3.0.1 and from sqlite to postgresql. Connected to Plex. When I click on my own profile, and a few others, I see a quick profile screen but it is immediately replaced with Oops Reutnr Home. Happening to Plex users as well as a local users. I'm getting the error on about 50% of my users.

Not much in the log files. I see this error occasionally but it's not when I am clicking on proifles.
2026-02-14T22:57:00.811Z [error][Plex.TV Metadata API]: Failed to retrieve watchlist items {"errorMessage":"Request failed with status code 401"}

#

I should mention I did have some issues moving from sqlite to postgres: https://discord.com/channels/783137440809746482/1472328640711884851

alpine stirrup Feb 14, 2026, 11:02 PM

#

Youll need to relogin

#

To update the plex token

#

Oh wait

#

Youre gettong oops?

#

Checked your console logs

#

From browser

#

I think a migration mightve borked somewhere

#

As in postgres migration

lone sage Feb 14, 2026, 11:05 PM

#

Nothing really in the logs. Strange that it's only some users. If I look in the users table, I don't see any glaring inconsistency. I can edit the user. but saving them doesn't fix the Oops error.

alpine stirrup Feb 14, 2026, 11:08 PM

#

lone sage Nothing really in the logs. Strange that it's only some users. If I look in th...

Console logs from browser when the oops returns

#

Not the logs from server

lone sage Feb 14, 2026, 11:12 PM

#

📎 seer-1771110667295.log

alpine stirrup Feb 15, 2026, 2:21 AM

#

lone sage

Ill take a look after i wake up

#

It seems related to media table migration

#

Or if you free CC: @wind elm

#

Imma go 🛌

wind elm Feb 15, 2026, 2:31 AM

#

really have to go to sleep too, can try to take a look tomorrow

lone sage Feb 15, 2026, 10:37 PM

#

Just checking to see if anyone had a chance to take a closer look at this one today? I noticed about 15% of my completed requests were coming up as Series Not Found. They were over a year old, so I deleted them all. Still getting the same error on the same users.

wind elm Feb 16, 2026, 10:29 AM

#

@surreal hamlet any idea?

alpine stirrup Feb 16, 2026, 10:48 AM

#

I know why

#

This comes from the old bug that was present

#

Which was fixed but old records need to be manually fixed

alpine stirrup Feb 16, 2026, 10:48 AM

#

wind elm <@258601459149570049> any idea?

Its the media null issue

#

@lone sage

SELECT id, type, status, "createdAt", "updatedAt"
FROM media_request
WHERE "mediaId" IS NULL;

#

Can you run this query directly in your pgsql

surreal hamlet Feb 16, 2026, 10:51 AM

#

alpine stirrup Its the media null issue

Yeah I thought we fixed this already

alpine stirrup Feb 16, 2026, 10:51 AM

#

And then send the results

alpine stirrup Feb 16, 2026, 10:51 AM

#

surreal hamlet Yeah I thought we fixed this already

It is

#

This is for old broken records

#

Which wont be magically fixed 🗿

alpine stirrup Feb 16, 2026, 10:52 AM

#

alpine stirrup Can you run this query directly in your pgsql

And then send me the output

lone sage Feb 16, 2026, 12:54 PM

#

Thank you. It returned 0 rows.

alpine stirrup Feb 16, 2026, 1:01 PM

#

lone sage Thank you. It returned 0 rows.

Run this

SELECT mr.id, mr."mediaId", mr.type, mr.status, mr."createdAt"
FROM media_request mr
LEFT JOIN media m ON mr."mediaId" = m.id
WHERE m.id IS NULL;

lone sage Feb 16, 2026, 1:02 PM

#

219 rows. Do you want the data?

alpine stirrup Feb 16, 2026, 1:05 PM

#

lone sage 219 rows. Do you want the data?

219 is a lot of orphaned requests

#

Likely during the sqlite -> pgsql migration, it didnt carry over all the media rows or the IDs shifted

#

You have two options. Retry the pgloader migration again (and this time update me along the way) or easiest way is to do the following

#

Try and reconnect any that can be connected

#

And delete the rest

#

SELECT COUNT(*)
FROM media_request mr
LEFT JOIN media m ON mr."mediaId" = m.id
WHERE m.id IS NULL
  AND EXISTS (
    SELECT 1 FROM media m2
    WHERE m2."tmdbId" = mr."tmdbId" AND m2."mediaType" = mr.type
  );

#

What do you get when you run this

lone sage Feb 16, 2026, 1:08 PM

#

LINE 7: WHERE m2."tmdbId" = mr."tmdbId" AND m2."mediaType" = mr....
HINT: Perhaps you meant to reference the column "m2.tmdbId" or the column "m.tmdbId".```

#

I don't mind losing old requests

alpine stirrup Feb 16, 2026, 1:09 PM

#

lone sage ```Error in query (7): ERROR: column mr.tmdbId does not exist LINE 7: WHERE m2."...

Oh wait wrong query. I'm just writing blind here so give me a sec 🗿

#

Yeah i just checked

#

Media request table doesnt have any tmdbids

#

So cant reconnect them

alpine stirrup Feb 16, 2026, 1:10 PM

#

lone sage I don't mind losing old requests

Lets delete the orphaned ones then?

#

First run this

DELETE FROM season_request
WHERE "requestId" IN (
  SELECT mr.id
  FROM media_request mr
  LEFT JOIN media m ON mr."mediaId" = m.id
  WHERE m.id IS NULL
);

#

Then

#

DELETE FROM media_request mr
USING (
  SELECT mr2.id
  FROM media_request mr2
  LEFT JOIN media m ON mr2."mediaId" = m.id
  WHERE m.id IS NULL
) orphaned
WHERE mr.id = orphaned.id;

alpine stirrup Feb 16, 2026, 1:11 PM

#

alpine stirrup Run this ```sql SELECT mr.id, mr."mediaId", mr.type, mr.status, mr."createdAt" F...

Then rerun this

lone sage Feb 16, 2026, 1:11 PM

#

178 rows affected in first one

#

219 in the second

alpine stirrup Feb 16, 2026, 1:12 PM

#

Damn so many orphans

#

sweating

lone sage Feb 16, 2026, 1:16 PM

#

I reran the second query and got 0 rows. No more oops on those users, but more Series not found. I can just delete these?

alpine stirrup Feb 16, 2026, 1:16 PM

#

lone sage I reran the second query and got 0 rows. No more oops on those users, but more ...

Yes

#

Th9se are orphaned media ids (or corrupted)

#

I also hated my migration process from sqlite to pgsql

#

Spent 8 hours

#

Rerunning them

#

To get it to work. Had to still remove 5 records

#

moyaicrying

lone sage Feb 16, 2026, 1:20 PM

#

Haha...it's not the worst for me. No one is paying me for this service 😜. And anything that was requested already made it to an arr.

alpine stirrup Feb 16, 2026, 1:21 PM

#

lone sage Haha...it's not the worst for me. No one is paying me for this service 😜. And...

For me im a huge stats nerd. I like to keep history

lone sage Feb 16, 2026, 1:21 PM

#

And some of them appear to be from watchlists, which are now starting to repopulate 🤦‍♂️

#

I hear ya....I normally am as well.

#

Interestingly, most of the ones i had to delete were from about 1 year in age or less....everything beyond that looks ok

alpine stirrup Feb 16, 2026, 1:23 PM

#

lone sage Interestingly, most of the ones i had to delete were from about 1 year in age or...

Thats atleast good news

alpine stirrup Feb 16, 2026, 1:23 PM

#

surreal hamlet Yeah I thought we fixed this already

So yeah not related to the bug but more so pgloader

lone sage Feb 16, 2026, 1:27 PM

#

Thank you for all your work on Seerr and the help with my issue. Really appreciate it!

#

Uh oh....back to Oops

#

I got 29 rows in that first query. Just run the last 2 again?

alpine stirrup Feb 16, 2026, 1:34 PM

#

lone sage Uh oh....back to Oops

Is the error still the same error?

#

In browser console?

alpine stirrup Feb 16, 2026, 1:35 PM

#

lone sage I got 29 rows in that first query. Just run the last 2 again?

Yeah try

lone sage Feb 16, 2026, 1:36 PM

#

Here is the console log. I'll try it again

📎 seerr.mydomain.com-1771248941048.log

#

BTW, I keep testing the same user. I didn't approve any new requests for this new user from their watchlist (it's disabled). So interesting that they would be impacted.

alpine stirrup Feb 16, 2026, 1:38 PM

#

lone sage BTW, I keep testing the same user. I didn't approve any new requests for this n...

Hmm. Maybe yoir entire media table ids no longer match

lone sage Feb 16, 2026, 1:38 PM

#

38 and 29 rows this time

#

Working again. This time no Series not found requests.

alpine stirrup Feb 16, 2026, 1:42 PM

#

lone sage Working again. This time no `Series not found` requests.

Can you send a screenshot

#

Sounds like your db is really messed 😭

surreal hamlet Feb 16, 2026, 1:43 PM

#

alpine stirrup So yeah not related to the bug but more so pgloader

And we have no other reliable way of doing the migration 🗿

alpine stirrup Feb 16, 2026, 1:44 PM

#

surreal hamlet And we have no other reliable way of doing the migration 🗿

We are at the mercy of pgloader 😔

lone sage Feb 16, 2026, 1:44 PM

#

Sure, which screen would you like to see?

alpine stirrup Feb 16, 2026, 1:46 PM

#

lone sage Sure, which screen would you like to see?

Hmm. Make a request. If it throws a series not found that

lone sage Feb 16, 2026, 1:49 PM

#

Made a new request. So far, no errors. User profile loads correctly

alpine stirrup Feb 16, 2026, 1:50 PM

#

Gingers crossed

#

sweating

#

FINGERS*

#

NOT

lone sage Feb 16, 2026, 1:50 PM

#

But...lol....Issues seem broken. I get an Oops when I change them to all

alpine stirrup Feb 16, 2026, 1:50 PM

#

https://tenor.com/view/củgừng-gừng-ginger-zingiber-gif-12311769

Tenor

củ gừng

▶ Play video

alpine stirrup Feb 16, 2026, 1:50 PM

#

lone sage But...lol....Issues seem broken. I get an Oops when I change them to all

Uhoh

#

Send the browser console for that

#

I think need to clear issues table too

wind elm Feb 16, 2026, 1:51 PM

#

surreal hamlet And we have no other reliable way of doing the migration 🗿

what if we write a script to load the sqlite data with typeorm, and then write the data to psql with also typeorm 🗿

alpine stirrup Feb 16, 2026, 1:51 PM

#

wind elm what if we write a script to load the sqlite data with typeorm, and then write t...

Actually

#

Not a bad idea

#

🤔

#

Cant be any worse than pgloader

#

Whats the worst that could happen? Break it more?

lone sage Feb 16, 2026, 1:52 PM

#

^ issues console log

📎 seerr.mydomain.com-1771249869625.log

alpine stirrup Feb 16, 2026, 1:52 PM

#

https://tenor.com/view/libradoink-gif-25433551

Tenor

wind elm Feb 16, 2026, 1:52 PM

#

alpine stirrup Not a bad idea

with typeorm it works when we retrive the info from sqlite, and it works when we update it to psql, so why not

lone sage Feb 16, 2026, 1:53 PM

#

I'd be happy to test 😁

wind elm Feb 16, 2026, 1:53 PM

#

then i'll write a draft tonight if i got time MoyaiSalute

alpine stirrup Feb 16, 2026, 1:55 PM

#

lone sage ^ issues console log

SELECT COUNT(*)
FROM issue i
LEFT JOIN media m ON i."mediaId" = m.id
WHERE m.id IS NULL;

lone sage Feb 16, 2026, 1:58 PM

#

1 row

alpine stirrup Feb 16, 2026, 1:59 PM

#

lone sage 1 row

Okay perfect

#

Only 1 corrupted one

#

DELETE FROM issue_comment
WHERE "issueId" IN (
  SELECT i.id
  FROM issue i
  LEFT JOIN media m ON i."mediaId" = m.id
  WHERE m.id IS NULL
);

#

DELETE FROM issue i
USING (
  SELECT i2.id
  FROM issue i2
  LEFT JOIN media m ON i2."mediaId" = m.id
  WHERE m.id IS NULL
) orphaned
WHERE i.id = orphaned.id;

#

And also run this following after the above

#

SELECT 'season' AS "table", COUNT(*) FROM season s LEFT JOIN media m ON s."mediaId" = m.id WHERE m.id IS NULL
UNION ALL
SELECT 'media_request', COUNT(*) FROM media_request mr LEFT JOIN media m ON mr."mediaId" = m.id WHERE m.id IS NULL
UNION ALL
SELECT 'issue', COUNT(*) FROM issue i LEFT JOIN media m ON i."mediaId" = m.id WHERE m.id IS NULL;

#

To do a full sweep

lone sage Feb 16, 2026, 2:05 PM

#

Rows: 6, 3 and 3

alpine stirrup Feb 16, 2026, 2:06 PM

#

alpine stirrup ```sql SELECT 'season' AS "table", COUNT(*) FROM season s LEFT JOIN media m ON s...

When you ran this you got a 3?

lone sage Feb 16, 2026, 2:06 PM

#

1st one returned 6 rows. Second one 3 and the last one 3 as well

#

Sorry, I should have written it out lol

alpine stirrup Feb 16, 2026, 2:07 PM

#

lone sage 1st one returned 6 rows. Second one 3 and the last one 3 as well

Did it not show a table

#

table          | count
---------------|------
season         | ???
media_request  | ???
issue          | ???

Something like this?

lone sage Feb 16, 2026, 2:08 PM

#

Sorry...yes:
table count
season 372
media_request 0
issue 0

alpine stirrup Feb 16, 2026, 2:09 PM

#

Oh dam 🗿

lone sage Feb 16, 2026, 2:10 PM

#

Issues view looks good now. No more Oops

alpine stirrup Feb 16, 2026, 2:10 PM

#

DELETE FROM season s
USING (
  SELECT s2.id
  FROM season s2
  LEFT JOIN media m ON s2."mediaId" = m.id
  WHERE m.id IS NULL
) orphaned
WHERE s.id = orphaned.id;

#

So all the orphaned seasons gets removed

#

Then rerun the last command again

alpine stirrup Feb 16, 2026, 2:11 PM

#

alpine stirrup ```sql SELECT 'season' AS "table", COUNT(*) FROM season s LEFT JOIN media m ON s...

This

#

To ensure it returns 0

lone sage Feb 16, 2026, 2:13 PM

#

table count
season 0
media_request 0
issue 0

alpine stirrup Feb 16, 2026, 2:14 PM

#

Perfect

lone sage Feb 20, 2026, 11:54 PM

#

So it was bothering me a bit that I had to drop a bunch of data. Like fallenangel, I'm a bit of a nerd with data and stats. I decided to try my postgres migration again with Claude AI's help. I'm happy to say after a bunch of back-and-forth, it was successful this time.

I thought I'd share a summary of what worked for me in case it helped anyone else or maybe to update the docs or look into the lastSeasonChange column. Apparently my source sqlite db had some corruption in it.

ETA: One additional step to fix the sequence numbers.

#Getting `Oops` Error when trying to view some profiles