Updated PMS to 1.15.4.994, appears to be running but cannot connect through browser

General Discussions
1

I have been successfully running PMS on a HP Gen 8 microserver running Ubuntu 16.04.6 LTS for the past five years. I will typically update Plex from the command line every few months (I might miss a version here or there and then catch up).

I updated to 1.15.4.994 this morning and now cannot see my server through a browser or through my phone app.

systemctl status plexmediaserver.service output returns this:

● plexmediaserver.service - Plex Media Server
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor
Active: active (running) since Tue 2019-05-14 12:38:45 BST; 8min ago
Process: 973 ExecStartPre=/bin/sh -c /usr/bin/test -d "{PLEX_MEDIA_SERVER_APP Main PID: 1008 (sh) CGroup: /system.slice/plexmediaserver.service ├─1008 /bin/sh -c PLEX_MEDIA_SERVER_INFO_VENDOR="(grep ^NAME= /etc/
└─1023 /usr/lib/plexmediaserver/Plex Media Server

May 14 12:38:45 dugbuntu systemd[1]: Starting Plex Media Server…
May 14 12:38:45 dugbuntu systemd[1]: Started Plex Media Server.

I am very much a Linux novice and have successfully kept my server running by figuring issues out through similar problems on forums, but this has got me stumped.

Logs attached. Any advice very gratefully received.

Thanks.

Plex Media Server.log (3.1 MB)

2

Are you using a VPN or reverse proxy? The WAN address is changing frequently.

3

Not on this server, no - although I do use a VPN on other machines on the network. I assume that wouldn’t make a difference though.

4

I’ve had problems with version 1.15 and would suggest that you downgrade to version 1.14 until they get this worked out.

5

OK - makes sense. Pardon my ignorance, but can you point me in the direction of a good tutorial for doing this? I have no idea how to roll back to my previous version of Plex.

6

Plex won’t update past 1.14 unless you manually downloaded the new file and did a dpkg -i.

Aside from all the strangeness in you log file, have you rebooted your router. The UPNP stopped working, unless you turned it off.

7

So - I actually did do a dpkg -i plexmediaserver_1.15.4.994-107756f7e_amd64.deb after wgetting (is that word?) the file from the URL on the Plex website.

Is that bad?

I have not, however, rebooted the router today (although I did yesterday). I will do so now and see what happens.

8

Router rebooted and no improvement.

9

The manual install is only bad in that you didn’t browse the forum ahead of time about all the possible conflicts with older installs.
If your not using a custom override.conf (systemd.conf).
Your system didn’t start life with init vs systemd.

Need to diagnose the WAN interface changes. Does your router have a status page that reports WAN IP?

10

My router does have a WAN IP settings page, that reports on my public IP, Mac Address, default GW etc. but not a status page as such. However, I have just noticed that the network status logs on the router are showing a bunch of critical errors associated with router’s MAC address, e.g.:

Warning! RCS Partial Service;CM-MAC=c0:05:c2:b6:b2:13;CMTS-MAC=00:01:5c:8a:64:c6;CM-QOS=1.1;CM-VER=3.0;

critical No Ranging Response received - T3 time-out;CM-MAC=c0:05:c2:b6:b2:13;CMTS-MAC=00:01:5c:8a:64:c6;CM-QOS=1.1;CM-VER=3.0;

Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=c0:05:c2:b6:b2:13;CMTS-MAC=00:01:5c:8a:64:c6;CM-QOS=1.1;CM-VER=3.0;

Possibly related?

Any suggestions on best approach for rolling back the 1.15 Plex install?

Thanks in advance.

11

After reading this thread - How to downgrade Plex (Ubuntu 16.04 LTS )? - I had a go at downgrading to an earlier version of PMS that I know worked - 1.14.0.5470. I used dpkg -i after wgetting the the file again and it all appeared to go smoothly.

My output from systemctl status plexmediaserver also appears to be OK (not that I really understand much from the output beyond the words in green saying ‘active (running)’. The output is:

● plexmediaserver.service - Plex Media Server for Linux
Loaded: loaded (/lib/systemd/system/plexmediaserver.service; enabled; vendor
Active: active (running) since Wed 2019-05-15 20:31:58 BST; 1min 4s ago
Process: 992 ExecStartPre=/bin/sh -c /usr/bin/test -d "${PLEX_MEDIA_SERVER_APP
Main PID: 1020 (sh)
CGroup: /system.slice/plexmediaserver.service
├─1020 /bin/sh -c LD_LIBRARY_PATH=/usr/lib/plexmediaserver "/usr/lib/
└─1023 /usr/lib/plexmediaserver/Plex Media Server

May 15 20:31:58 dugbuntu systemd[1]: Starting Plex Media Server for Linux…
May 15 20:31:58 dugbuntu systemd[1]: Started Plex Media Server for Linux.

I am still unable to connect through a browser, either over the network from my laptop or localhost when I VNC directly onto my server (which is also running Gnome). Also, my PMS server logs do not seem to show any new activity since May 14 when I broke everything after upgrading. This seems at odds to the status message of ‘active’ showing above.

My other apps (Sonarr and NZBGet) are all still running fine.

Any suggestions for next steps gratefully welcomed.

12

I would periodically check https://www.whatsmyip.org/ to see if your WAN IP is changing, the does look like a bad connection or failing modem.

13

The error except from the log (full log ZIP would be best if possible) shows

Error	DHCP REBIND WARNING - Field invalid in response;CM-MAC=c0:05:c2:b6:b2:13;CMTS-MAC=00:01:5c:8a:64:c6;CM-QOS=1.1;CM-VER=3.0;

Also please check DNS Rebind allowance for private domain plex.direct
Plex won’t be able to find everything on your LAN without it.

14

Hi Chuck,

Thanks for getting involved. Much appreciated.

My crappy Virgin Media Router doesn’t keep much in the way of logs. It looks as though the networks logs are limited to 20 entries (sigh) - so I’ve attached those.

Network Log.txt (2.7 KB)

I have also just discovered that Virgin Media Superhub does not allow you edit DNS settings.

Nevertheless, my gut feeling is that it is not a DNS rebind issue (although I appreciate that I’m seeing some rebind errors in the logs) on the basis that I cannot even connect to the plex interface using a browser on the local server itself. I assume that I should still be able to connect using localhost::32400/web/index.html# even if there was a rebind issue happening here?

The other consideration is that this stopped working directly following a plex upgrade. I have since tried to roll back to two different version of 1.14, but still no joy. systemctl status plexmediaserver is still reporting that Plex is running.

Any suggestions on what to try next would be welcomed.

15

Hi @duggy_blueyonder_co_uk,

I have exactly the same issue on my server - recently I’ve upgraded my plex from version 1.13.4.5271 to version 1.15.4.994 and I cannot see my server through a browser, currently I’m getting information “Looking for servers” (I’ve described my issue here: https://forums.plex.tv/t/a-server-could-not-be-found-after-upgrade-to-1-15-4-994/)

As you can see I’ve tested multiple versions of plex server and non of them works - I had to downgrade plex server to version 1.13.4.5271 to make it works.

Regards,
Matt

16

Hi Matt,

Thanks for the feedback. Can you share the URL for that version of plex? I can give it a try.

Duggy

17

OK - update. I got to the bottom of it (I think).

After trying a few different older versions and not having any luck, I decided to take a look to see if there were any obvious config changes I could see.

I discovered that my /{usr,var}/lib/plexmediaserver folders were now owned by root and not user:group plex:plex (which is how I remember I set things up). This can only have happened when I tried to upgrade.

I used chown -R plex:plex /{usr,var}/lib/plexmediaserver to change both folders and I seem to be back in business.

Thanks to everyone for their time and thoughts on this.

The support and willingness to assist on this forum is truly amazing when I consider what ■■■■ support I get from so many services I pay for in my life. Thanks again for all input.

Duggy

1 Like
18

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