Not seeing the option to add libraries or see server settings

Server Version#: Latest
Player Version#: 4.59.2

So I had to remove Plex from my Linux server, and I reinstalled it. I removed all the config files, but now when I go back into Plex on my local IP, I didn’t see the option to do the initial config, I don’t see server settings available to me, and I don’t have the option to add libraries.

What might be happening to cause this, and how can I resolve it?? The drives are still mapped, and the video files are still in the same place on those drives.

https://app.plex.tv – get into the desktop .

Settings - Authorized Devices - SERVER dropdown

REMOVE the server which is now gone.

Sign out of Plex/Web

close browser tab, open fresh, https://lan.ip.of.server (or loopback )

Couple of things, I didn’t have a SERVER in the dropdown list, I had all devices, and the other devices that had a attached, but the server wasn’t listed

I did sign out of https://app.plex.tv and then went to my local device in a separate window, I wasn’t asked for a password, it signed me in automatically, and I still have the same issue

@SteveG144

  1. IP address of computer ?
  2. IP adddress of the machine you’re accessing ? (assuming on same RFC-1918 compliant LAN subnet ) ??
  3. Distro?
  4. Container or bare machine?
  5. whatever else describes the details of the installation

My laptop is on 192.168.50.1/24 network
The server is on a 192.168.0.1/24 network - there is vlan traffic allowed between those 2 ranges
This is on Ubuntu: 20.04.2
Bare machine

I had it running before and had a problem. Did a uninstall and also removed the preference settings. Reinstalled with dpkg -i plexmediaserver_1.19.3.2852-219a9974e_amd64.deb

After going back into the IP of 192.168.0.101:32400 it says the home screen is empty and I don’t see the full range of settings options when I go into settings

Steve,

  1. VLAN be dammed. PMS doesn’t care about switching. Are you confusing VLAN with Subnet ?

  2. PMS looks at the subnet and mask. 192.168.0.x/24 subnet in this case.

  3. If the host is not claimed, which it won’t be on first install, you must be on the same TCP/IP subnet
    -or-

  4. SSH into the box and claim it via the loopback adapter the the Plex Claim Token method (usually easier).

I your laptop is now back on that subnet, if you don’t have server settings then it’s still not recognizing you as the owner (Not claimed)

Let’s do the following:

  1. Determine its status - it should be unclaimed ( claimed="0" )
    type: http://ip.addr.of.server:32400/identity

  2. if unclaimed (let’s presume this is true ), SSH into the machine

  3. make certain PMS is running

  4. In your browser , Claim | Plex

  5. It will show you a claim token

  6. COPY that to the browser

  7. Now, back in the ssh window, type

curl -X POST ‘http://127.0.0.1:32400/myplex/claim?token=PASTE_THE_TOKEN_HERE

(don’t forget the closing quote)

It will look like:

curl -X POST 'http://127.0.0.1:32400/myplex/claim?token=claim-XXXXX'

  1. you only have 5 minutes so don’t be too slow but don’t make a mistake either else you’ll need start over.

  2. this will pause for about 10 seconds while PMS and Plex.tv negotiate.

  3. It will then print out a whole bunch of “Feature flags” (what your account has)

  4. Now, the server is again attached to your account. You may use it normally as you did before

On step 1 -determine its status, I’m getting a 401 Unauthorized error

And no, I’m not confusing subnet vs vlan. I have multiple vlans in the house, the wifi is attached to one and has its own range, and the wired is on a separate vlan :slight_smile:

had something similar with some plex web display weirdness.

go to settings > plex web > debug and hit the “RESTORE DEFAULTS” button.

401 ?

Are you using a cert?

It should still respond with claimed or unclaimed using the loopback adapter.

That’s how Plex/web and services work on the host work

Ok, I did get it to work, thanks for your help :slight_smile:

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