Can't get PMS to appear in Authorized Devices list

Plex Media Server
,
1

Server Version#: 1.25.1.5286-34f965be8
Player Version#:

Logs:
[services.d] starting services
Starting Plex Media Server.
[services.d] done.

Hi, I have just created the Plex Media Server using the official docker image. Unfortunately, I cannot get the device to appear under Authorized Devices. There’s nothing interesting in the server logs (see log entries above). I used a claim token, but just in case, I also used an SSH tunnel to log in when the browser was pointed at http://localhost:32400. That logged me into the web player but nothing seemed to change with the media server.

I’m at a loss for what to try next.

2

@endotronic

Sign out of Plex/web first.

Now open an incognito window

In that incognito window you can access the server.

BEFORE doing all that, I must ask if you have your docker container configured with --network=host or have you allowed it to default to NAT?

If you have it set --network=host then it will be the same as a native app on your host. NAT or Bridge will require tunneling – which is always messy

3

Thanks for the quick reply. I was hoping to use bridge networking. I used to do this successfully (with Plex) and prefer it. I’m fighting with this today because in trying to solve a connectivity issue, I removed the server from Authorized Devices, and now I can’t get it back. I didn’t think the networking mode should have much impact on whether it authenticated the server or not, and I don’t mind tunneling to log in once. Anyway, I switched to host networking, and now after log in, I get an endless spinner.

I believe my connectivity issue was that I had the environment variable ADVERTISE_IP misconfigured. It was set to an old IP address; the server now has a different LAN address. This is updated now, but sadly not before I removed the server from Authorized Devices.

FWIW, I can access the web app both from localhost:32400 when tunneling into the server and from the address configured for ADVERTISE_IP.

4

Hold on! I capriciously refreshed the page with the endless spinner and managed to set up my server. This is progress, awesome!

I also just confirmed I can access the server from other devices. I’m going to try bridge networking again, but this is already a solution.

5

Recreating the container with bridge networking worked perfectly (using the same persisted configuration directory). It just needed to be created with host networking I guess.

6

Bridge networking allows it to share the adapter – AND – have its own IP address

(go look and you should see a new host entry which is the container).

Establishing that new ‘host’ on the lan and populating it via Plex.tv is just like reclaiming. (which you managed to do )

7

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.