Media Missing

Plex Media Server Desktops & Laptops
1

Server Version#: 1.29.2.6364-6d72b0cf6
Player Version#: any current version on Windows, iPhone, Apple TV, or Web.

I can’t say whether I can correlate the behavior with the last update because I don’t remember when I noticed the last plex update on my server (ubuntu headless 20.04), and I update frequently.

It’s as if Plex thinks my server media has disappeared. When I log in to plex web, app.plex.tv/web/app, I see “Add your media to Plex.” I can access the media folders outside of Plex just fine, there has been no change. Even the logs indicate that it can see the media.

I have tried to delete the server from Authorized Devices and then go through the process of reclaiming the server. Nothing works. I stop the service, delete the properties from the Preferences.xml, start the service, tunnel in through putty, open the tunnel in my browser on my desktop, go to settings, click general, click claim server, sign in, it shows a loading wheel, the page refreshes and displays the error “Not Authorized. You do not have access to this server.” The server shows up again in Authorized Devices. Will not connect to media.

2

I think you’re on the right track, re-claiming. Why it didn’t work? Well, there are a number of variables. So let’s just try to get you back up rather than putz around.

Step 0: Power cycle every piece of hardware in your network and your Linux box.

In another topic I explained for Mac how to Reclaim from the command line and you could follow steps (1) (5) & (6) in the tunnel, then grab :beers: cuz that’s gonna work.

I suggest that you clear your history, cookies and cache, then restart the browser. That way you’ll get a nice Plex Sign-in when you use Plex | Claim.

3

I need you to be more specific. Obviously, I’m not using a Mac, and I am using headless ubuntu so no GUI to open a browser for the claim code. I opened the claim code page on my desktop and copied the code into ssh terminal using the command instructed: curl -X POST "http://127.0.0.1:32400/myplex/claim?token=<thetoken>"

Terminal spits out: "<html><head><title>Internal Server Error</title></head><body><h1>500 Internal Server Error</h1></body></html>"

4

I would recommend trying Server credential reset utility for Linux-based platforms and reclaim it that way.

5

I have tried to delete the server from Authorized Devices and then go through the process of reclaiming the server. Nothing works.

I tried that already

6

A few things.

  • I knew you could handle a curl and a browser window or would at least try, and you did great.
  • but lets double check. Say I got the code claim-12scoobydoo34 then I would use
curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-12scoobydoo34'
  • So let’s guess you typed the exact curl correctly, but you get an error 500. At least PMS had started and was listening on port 32400.
  • That’s a very uncommon error. The only other time I’ve seen that is starting with 1.29.2.
  • The fact that the linux claim utility doesn’t work is also an indication of something abnormal.
  • Before you do too much, please grab the server logs so the developers can look for anything obvious, and drop the zip file into your reply.
  • The most common way to get back to a sane server is to roll back to an earlier version.
  • I would suggest testing 1.28.2.6151 after you get the logs because it has always been solid.
8

Not one ERROR message, and barely a WARN in that Plex Media Server.log.
It can see all your media. It seems happy enough from the surface.

@dane22 @ChuckPa

User getting http Error 500 trying to reclaim from the command line, headless ubuntu,
and even the Credential Reset Utility doesn’t work.

9

many people in the thread you linked above seem to be having the same problem

but their recommendation to downgrade to 1.29.0.6244 did not work for me.

I also tried upgrading to 1.30.0.6406 and the issue persisted.

I cannot find a download to 1.28.2.6151 as you suggested.

I will downgrade further to 1.28.0.5999.

10

Sometimes you can find past versions in your PMS directory called Updates.
Plex has the old versions, and in that same topic, up around post 35, is a giant example of maybe two dozen old versions for Mac.

You can replace a couple of key words in the URL and build the correct link for your OS.

When deciding on a reasonable previous stable to try, not a beta, I use the forum Announcements topic to see which one was stable. Any should suffice, but 1.28.2 was recent and is worth trying.

11

No luck.

No matter which version I use, apparently, I go through the re-claim process, tunnel, open a private browser, go to 'localhost:8888/web/`, click “Claim Server,” log in, it shows a loading wheel, the page refreshes, and then I see “Not Authorized. You do not have access to this server.”

I have also tried it the way you suggested before, by creating a claim token and using curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=<thetoken>' but I just get error 404 on that. Are you certain it’s the correct URL?

12

The process is a few pedantic steps.

  1. Quit PMS and reboot the hardware.
  2. sign PMS out remotely by removing it from Authorized Devices
  3. sign PMS out locally by removing the entries from Preferences.xml
  4. clear cookies cache history
  5. install different version == NOT something you want to do each time.
  6. start PMS & wait about 10 minutes if you changed versions. It’s migrating the DBs.
  7. claim from the command line.

I can see you’ve referred several times to tunneling into your headless.
Please explain why you and your headless are not on the same subnet such that you have to tunnel. Normally I just open a ssh terminal to the IP of my server.

I can see you tried several ways to claim, but after every attempt you have to pedantically follow the steps to log out.

Yes I’m sure of the exact url. If the headless is at 192.168.1.10 why not just ssh there?

13

The last logs were completely filled with it migrating your db.

14

Those steps you outlined are essentially what I do every time, except as I described, I cannot claim from the command line (assuming you’re suggesting the curl method).

My initial attempts to reclaim were done so by just using the local IP (192.168.1.10:32400/web), I had read that it’s better to claim as the machine itself (localhost/127.0.0.1:8888/web) which can only be done if I tunnel, so… that’s why. it’s a small procedure as putty has the config saved so it’s not a lot of trouble. though, effectively the same process, I agree. But this is only if I’m trying to claim by using the browser. If I’m attempting to use the curl claim method, then I wouldn’t bother with the tunnel.

I will restart the service and wait longer before I post new logs. migrating the DBs was not something I had taken into account.

15

Please just ssh to 192.168.1.20 from your laptop and don’t tunnel.
We can avoid a layer of abstraction for now, even though it’s totally possible.
I’m not good enough at those to easily spot a typo, and frankly it’s not needed if both PMS and your laptop are on the same RFC compliant private subnet, 192.168.1.0 / 24 in this case.
That is the requirement for claiming and administering PMS.

I can’t tell you how many times I failed to install PMS on a Mac until I sorted out the steps.
I just expect yours to be smoother as long as you do them.

16

Re-read my last post as i’ve edited to clarify

17

I just tried the curl method once more and it actually returned the XML data that you said it was supposed to this time.

I’m afraid to do anything else. What do I do next?

18

it worked go watch a movie :slight_smile:

19

i’ll try logging in

20

May I be of help here?

21

Thanks for stopping bye. I think he just got it claimed. Give him 2min.