Fresh Docker install and unable to claim server

Plex Media Server NAS & Devices
1

Server Version#: Version 1.32.5.7349
Player Version#: N/A

So I had issue where my library wasn’t visable outside my home network and wasn’t showing up in my settings. That happened randomly after Plex had been working fine for over a year. I removed the server from authorized devices, and then deleted the container and volume thinking that was the easiest way to resolve the issue. However now I cannot claim the server no matter what browser I use

OS: Running in Docker on Open Media Vault 6 (Linux)

Clients, w/ versions, if applicable: Plex web client direct through the local IP http://192.168.1.101:32400/web/index.html and tried on Safari and Firefox

What you did? I had some issues with my Plex server not showing up outside my house after some internet problems, so I did a clean install of removing my old server as an authorized device, deleting the container and volume and then recreating it. I then got an issue where in the start page it tells me there’s an issue with Plex login and when I press the “claim server” button nothing happens.

I tried then deleting the container and volume and redoing setup in a private browsing window but that didn’t work.

I tried adding an env variable “Plex_CLAIM” with the token from https://www.plex.tv/claim/ but that did not work either. I tried it twice, one with the preceding claim part and once with just the string after the dash.

Following this guide I tried editing the preferences.xml file but all I saw was PlexOnlineToken=" " but to be safe I deleted it anyway. I’m still unable to claim the server.

What are your (relevant) settings? I followed these steps when setting up plex in docker aside from adding the GID/UID. How to Install Plex on OpenMediaVault - WunderTech

Link to logs (optional but recommended):

GID/UID

───────────────────────────────────────

User UID: 1000

User GID: 100

───────────────────────────────────────

**** Server is unclaimed, but no claim token has been set ****

**** permissions for /dev/dri/renderD128 are good ****

**** permissions for /dev/dri/card0 are good ****

Update routine will not run because you havent set

the VERSION variable or you opted out of updates.

For more information checkout :-

GitHub - linuxserver/docker-plex

[custom-init] No custom files found, skipping…

Starting Plex Media Server. . . (you can ignore the libusb_init error)

sendto: Network unreachable

sendto: Network unreachable

sendto: Network unreachable

sendto: Network unreachable

[ls.io-init] done.

sendto: Network unreachable

sendto: Network unreachable

sendto: Network unreachable

sendto: Network unreachable

1 Like
2

@ChuckPa The same problem here. I am currently using hetzner to share between my families houses but after I restarted and it tried to update the server is now unclaimed and I get " not authorized " when loading.

3

May I get actual DEBUG ZIP files / tar.gz files please
(@Pryrt and @macgyv1 )

Network unreachable is a local host problem. It means there is a configuration error in the host. I would like to see the Logs to confirm the actual errors. On a regular host (native install), it means the ethernet adapters aren’t configured for the subnet it’s on and/or the LAN broadcast address is blocked. That’s why I need to see the logs

4

it looks like you already are working on a fix per Can't claim server - #12 by ChuckPa

5

“Can’t claim server” is a Hetzner problem.

The “network unreachable” is independent of that.

6

(redacted after issue solved)
I’ve attached the zip file of the logs.

I’m not using Hetzner and I don’t know why there would be a networking issue when I configured it the same way I did last time.

I appreciate any help, I’m truly stuck.

7

@macgyv1

Your container cant get out of the host to the internet.

Sep 18, 2023 19:58:30.458 [139780302527288] WARN - [HttpClient/HCl#5] HTTP error requesting GET https://v4.plex.tv/pms/:/ip (7, Couldn't connect to server) (Failed to connect to v4.plex.tv port 443 after 4 ms: Couldn't connect to server)
Sep 18, 2023 19:58:30.458 [139780277742392] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-7): 
Sep 18, 2023 19:58:30.459 [139780302527288] WARN - [HttpClient/HCl#6] HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxxt to server) (Failed to connect to plex.tv port 443 after 5 ms: Couldn't connect to server)

Do you have it set as “Host” or “Bridge” or “NAT” networking.

I use HOST networking to keep it simple.

8

I have it in HOST

9

go to the command line

nslookup plex.tv

also config you can open https://app.plex.tv

10

So when I try nslookup plex.tv in commandline it tells me that nslookup command isn’t found. When I go to setting > manage > console it doesn’t let me input any commands.

When I open plex via the app or the app url I can’t see the media in my library that I can with the local ip.

11

Do nslookup on the host.

when the server gets claimed (can talk to plex.tv)
then the media will show up

12

it’s still telling me command not found, when doing it with the console attached to the container (through portainer)
image

I just entered ls -l to show commands do work on the console

13

get out of the container

get back to your OS.

What’s the OS you’re on? OMV ?

14

Open Media Vault 6

15

There’s a special trick to Plex in OMV.

We don’t officially support OMV so I don’t have any documentation at the ready

I do have Proxmox LXC info but even that’s dated.
( I use LXC’s myself on Ubuntu which are hugely easier )

Have you done a google search for Plex+OMV 6 ?

16

So I figured out the issue, that I had improperly configured the gateway settings on my server, and then confused my issues with not being able to claim a server with other people’s issues of not being able to claim the server but theres had a different cause. Thanks for helping me troubleshoot this a lot, I wouldn’t have thought to go back and look at my server settings.

17

so it was network. That’s what it behaved like.

The lack of DNS failure was throwing me.

I’m VERY glad you found it.

1 Like
18

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