Server Version#: 1.21.4.4079
Player Version#: Web Player 4.51.3
I just recently did a hardware swap on my old fileserver, and in the process ended up needing to reinstall Ubuntu Server. I decided to go ahead and switch over to 20.04 and just rebuild the server completely. Samba and mdadm have both set up and operated fine, but Plex seems to be having issues. It won’t allow me to claim the server (it simply spins for about a minute before the button just comes back), and attempting to play movies eventually fails. Movies are getting scanned from the library and are correctly updating metadata from scanners, and I’ve made sure that plex is the owner of the folder and subfolders / items for the movies.
I’ve now tried 4 reinstalls of PMS, once via plex-updates and the others via dpkg of the .deb for the latest version. In between reinstalls I’ve removed the plexmediaserver folder from /var/lib/. My router has uPnP enabled and I can see that there is an entry for the 32400 internal port for the server. I’ve tried clearing uPnP entries to allow it to reconnect and I’ve tried manually forwarding the port, neither of which worked. The server does not have a firewall enabled at the moment that I’m aware of (checked for ufw which is disabled at the moment, don’t believe any others are included by default on Ubuntu Server).
This machine was working fine before the swap of hardware, and I had to reinstall because both the graphics and network adapters wouldn’t launch correctly after the swap, so I had no way of accessing the server correctly. There’s been no other change to the network, and the machine is capable of pinging app.plex.tv (can’t ping plex.tv but that seems to be related to plex.tv and not the server). I’ve also tried disabling ipv6 support and manually selecting the correct ethernet interface from the web interface (:32400/web, which is accessible).
Any help would be appreciated, I’ve tried crawling through all the previous discussions on the forums and nothing ended up fixing what I’ve encountered. Logs should be attached, I just restarted the service and attempted to claim before pulling the latest log files so that should show everything of relevance to that issue (hoping the player issues are related to the claim issues).
Ping test to app.plex.tv from the server’s terminal gives me a response, and the scrapers seem to be functional (I’m getting all the info about a movie when I select it: ratings, actors, summaries, reviews, etc.), so I am under the impression that it’s getting proper access. I can also see that it has an entry under the UPnP table for my router, internal port 32400, external port in the 20000-50000 range. Using my external IP and the specific port, I can get to the web interface which prompts me to sign in and warns me that the server is not hosted by plex.tv, but then I get the “No Soup for You” page once I actually try to access the libraries.
Both computers are on the 192.168.1.xxx network, same subnet mask (255.255.255.0) per ipconfig/ifconfig, and gateway is the same. I did notice under ifconfig in the server that there are 3 networks listed: docker0 on 172.17.x.x, enp2s0 on 192.168.1.xxx, and lo on 127.0.0.1. Those are all expected but I suppose it’s worth giving the full picture. I selected enp2s0 under “preferred network interface” under the server settings for “Network”, as that’s my internet-facing interface.
This finally seems to have done it. I went through it several times and was getting a 500 error, so I tried a couple things. Eventually it came down to setting both the DNS of my Ubuntu machine and my router to 8.8.8.8 and 8.8.4.4, instead of the OpenDNS servers (208.67.222.222 and 208.67.220.220). After that it was having issues with UPnP, it seems, but a manual port forward setting seems to have fixed that easily.