Can’t Claim Server

Server Version#: 1.41.1.9057

Hi,
I can’t claim my server. I am running Plex on a Raspberry Pi 4b (installed via Repo (Debian Bookworm base)). I can log into Plex fine and when I go to claim the server, it tells me there was a problem logging onto Plex, and won’t let me Claim the Server, I’ve tried different logins to no success. I am also told my version is out of date, I have the latest version

There are a few restrictions when claiming:

  1. You must open the server in your browser by its IP address. Using a FQDN will invoke the security flag and block claiming.

  2. You must be on the same RFC-1918 subnet as the server.

  3. When all else fails, Stop Plex, make a tar.gz of the “Logs” directory under “Plex Media Server” and attach it here.

OK, so I am;

  1. Opening my Plex server by it’s ip address, I am connected to the same router that the server is connected to, let’s say the server is http://123.456.789.000:32400. I am accessing http://123.456.789.000:32400 via my laptop (who’s IP is 123.456.789.001, for example)…
  2. I would assume that if I am on the same router I should be on the same SubNet as the server. I have even tried accessing the server via VNC and registering it off the server itself via the servers local IP (http://123.456.789.000:32400).
  3. Logs attached…
    Plex Media Server Logs_2024-11-02_21-28-38.zip (155.4 KB)
    Plex.log.zip (160.5 KB)

Thanks for the logs.

Your network configuration is in rough shape.

  1. You turned off DEBUG logging – I can’t see what it’s actually attempting to do.
  2. What I can see is network failure trying to configure PMS for the local LAN
Nov 01, 2024 23:25:03.071 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.071 [547611115744] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:261:33 in function 'send_to']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:261:33 in function 'send_to']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.092 [547632513248] WARN - [HttpClient/HCl#4] 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 46 ms: Couldn't connect to server)
Nov 01, 2024 23:25:03.092 [547638276320] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-7): 

Best advice here is to examine the network configuration.

  • Make certain you have one of the adapters configured as the default adapter/gateway.
  • Make certain your DNS is either pointed to a public DNS IP or your modem/router

I advise turning on DEBUG logging again ( logDebug="1" in Preferences.xml) temporarily so you can better see what’s happening while debugging then turn it off again when done.

Hi,
I have attached Debug logging now…
Plex Media Server Logs_2024-11-02_22-28-45.zip (183.4 KB)

When I went into my network settings I noticed I have two hardwired ETHERNET connections, so I removed on of those and disabled the WiFi connection too… so there is just one connection now…

I am looking into the multicast stuff now :confused: Hopefully these new logs will shed some light :confused:

ip a reveals this…

eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether dc:a6:32:6f:6e:84 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.243/24 brd 192.168.1.255 scope global eth0
       valid_lft forever preferred_lft forever
    inet6 2a00:23c5:5412:ac01:dea6:32ff:fe6f:6e84/64 scope global dynamic mngtmpaddr 
       valid_lft 280sec preferred_lft 100sec
    inet6 fe80::dea6:32ff:fe6f:6e84/64 scope link 
       valid_lft forever preferred_lft forever

Thanks for the debug logs.

I can see a bit more.

Make certain the date/time (clock) on the machine is in sync with NTP servers.
If not, you’ll not get HTTPS to Plex.tv

There still appears to be a network config problem.

Yeah, I am not sure what it is, as looking into the logs I see that I switch from a 192 IP address to a 127 based IP, for… reasons…

The ethernet adapter is either 192.168.x.x, 10.x.x.x, or 172.16.x.x → 172.31.x.x

127.0.0.1 is the loopback adapter

Could you highlight the network config issue for me please?

Nov 01, 2024 23:25:03.071 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.071 [547611115744] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:261:33 in function 'send_to']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - NetworkService: Couldn't join multicast group: set_option: No such device [system:19 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:174:33 in function 'set_option']
Nov 01, 2024 23:25:03.072 [547611115744] ERROR - Error broadcasting message: send_to: Network unreachable [system:101 at /home/runner/actions-runner/_work/plex-media-server/plex-media-server/build/dependencies/plex-media-server/standard-aarch64-linux-musl/boost/include/boost/asio/detail/reactive_socket_service.hpp:261:33 in function 'send_to']

The multicast address range is 224.0.0.0 through 239.255.255.255 and defined by the host

I don’t know what that is? I have a Docker bridge setup, but that shouldn’t be interfering (the 172… IP). Could there be a dependency missing? or is this purely configuration…

This is purely host configuration – (possibly host configuration corruption too)

I am not actually sure what is wrong here… I’ve had to rebuild my Server recently (Raspberry Pi4b w/ Debian Bookworm), and now the networking isn’t working properly, when it was before I rebuilt it. So you can understand why I am struggling… As this should be working out of the box…

At the base level… let’s confirm the host is ok

sudo apt update
sudo apt -y upgrade

It should be able to go get updates and upgrade without errors.

sudo netstat -rn to confirm you still do have a valid routing table

I’ve fixed it by losing my sh*t and reformatting the whole server and starting from scratch, as you said it could have been a corrupted network config, so I wiped everything out and started again, again.

My apologies for being a massive waste of time

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