I’m running Plex media server 1.32.5.7349-8f4248874 on Ubuntu 22.04.2 LTS. I recently tried a fresh install after the problem described in a previous post:
But now after a new install Plex won’t start at all.
I have the logs but it’s unclear how to attach them to this post. In /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Logs/Plex Media Server.log, there are no errors.
logs.tar.gz (62.5 KB)
Please do the following:
Now wait 4 minutes for Plex to complete first-time initialization before you open it.
(don’t do anything. just let it sit there)
Your logs show PMS trying to be more active than it’s ready for.
Also, you show a WAN (Public) IP address in addition to your 192.168.0.100 default machine address. This might cause you networking problems depending on how you’re using it.
Thanks for the response! I followed those steps, waiting around 10-15 minutes before trying to log in. but now the web UI at 192.168.0.100/web just says the server is offline.
I’m attaching the new logs from this latest attempt.
logs.tar.gz (88.3 KB)
Edit: I restarted plex (systemctl restart plexmediaserver), waited about 5 minutes, and tried the web UI again. This time it spun and I get the same message as in the earlier screenshot.
Thank you for the logs.
They are showing me what looks like a network problem.
There is a San Jose IP address defined on the host.
Is this a VPN or something special? (I see a different location where you last signed in from)
Is PMS running in a VM ?
Thanks again for responding. The 107. Address is the public IP NATed to plex’s private 192.168.0.100 IP. it’s not running in a VM or behind a VPN but it is on a host with both a public (the 75.* address) and a private (the 192.168.0.100 address) interface
It’s run this way for years and I had never had this problem before. Is there a way to force plex to only use one IP and ignore the other?
I’m not too worried about the IP addresses – YET! lol
I would like to ask if you’ve tried opening the server –
If this doesn’t work,
I have a tool which will help with the claiming part
I’m not using the browser from the same machine Plex runs on; the browser is on a Windows 11 machine, PMS is running on a Ubuntu machine. They’re both on the same 192.168.* subnet. So hitting Plex via 127.0.0.1 won’t work.
When I tried from a private Firefox browsing window (to http://192.168.0.1:32400/web) it asked me to sign in to claim the server, which I did, but then Plex did the same thing – it spun for awhile and failed to start, showing me the same “A problem has been detected…” screen.
There are too many successful installations of PMS on Ubuntu to be PMS.
This has to be something with how the OS is installed & configured.
That said, do you have Ubuntu 20.04.6 LTS to install?
Is that something you can do on the host?
(FWIW: I always configure a /home partition on PMS hosts so I can save important stuff in case I need to change the OS itself. ‘/home’ can be included in a new OS installation without force-reformatting it)
You also must make 100% certain your PC is on the same LAN subnet as the server when you claim it. That is critical (unless you use a claiming tool)… when we get that far
I gave up and installed PMS on my Windows 11 machine. It set up and worked flawlessly in minutes.
Luckily I don’t really use PMS for anything but sharing random things with friends; for my own personal media collection I use Emby. (Emby runs fine on the current Ubuntu 22 box, as do OpenVPN, Jellyfin, Navidrome and many other services. Only Plex has issues.)
I really appreciate all the help! I will say that I disagree that most Ubuntu installs being successful means any unsuccessful Ubuntu install indicates an OS problem. To me this looks like a very strange and undiagosed PMS bug. If this were an OS issue I suspect I’d see issues in other applications and in the functioning of the OS itself.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
