Remote Access Issues Again

Plex Media Server Desktops & Laptops
1

Server Version#: 1.14.0.5468
Player Version#: 3.77.1

I’ve just been able to troubleshoot one of my servers. After looking through the forums, I noticed a lot of people having remote access issues with the Linux PMS. I downloaded the newest update and I’m still not able to connect. I’ve restarted the server and reinstalled PMS. I would have added to an already existing topic but all of them were closed immediately after some people experienced success. I have remote, not physical, access to this machine. Logs below.

Plex Media Server.1.log.zip (138.3 KB)

2

On same version with same problem it seems, just seems to be not working as of 2 hours ago. Tried a couple of things, but remote seems broke again :slight_smile:

3

First time i come across a system with so many network interfaces

Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG - Network interfaces:
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 1 lo (127.0.0.1) (loopback: 1)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 2 eno1 (192.168.1.111) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 7 br-0057c786c2f4 (172.20.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 8 br-19cf28c68eca (172.19.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 9 docker0 (172.17.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 10 br-b32060d4dca8 (172.25.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 11 br-b5e0aa4962d6 (172.23.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 12 br-f9f89800273d (172.22.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 13 br-2f000424bf4f (172.24.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 14 br-63e8a26ccf60 (172.21.0.1) (loopback: 0)
Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG -  * 15 br-b8a6d5bf62a2 (172.18.0.1) (loopback: 0)

The log shows attempts to connect to your server through your chosen public port are failing to get through

Nov 23, 2018 12:48:13.517 [0x7f81f04b6840] DEBUG - Detected primary interface: 192.168.1.111
Nov 23, 2018 12:48:41.337 [0x7f81e1bff700] DEBUG - EventSource: Got event [data] '<Message address="66.211.xxx.xxx" port="8080" asyncIdentifier="d67a4ce8-c4fd-45af-a58e-8cf4e6aa9925" connectivity="0" command="notifyConnectivity"/>'

Is it possible that the port forward in the router got lost ? eg after an ISP router update?

Could you show me screenshot of the port forward in the router to forward WAN port 8080 to LAN port 32400 and route to 192.168.1.111

Any new security software that may be blocking the attempts to connect to the server from the plex.tv amazon aws servers?

4

@sa2000 - Me too. Not sure why this server has so many interfaces. I bought it reconditioned with no OS. Installed Ubuntu 18.04 and there are all of these (I can only assume) virtual network interfaces. Nonetheless, the proper address (192.168.1.111) has always mapped correctly. No new security software. Here’s the screenshot of the router settings. I rebooted the router as well. No luck. I should point out that every once and a while I receive a notification that Remote Access is up, but almost immediately it goes down again. Makes me wonder if the problem may be the connection to the Plex backend?

Router_Settings
Router_Settings855×585 48.3 KB

Edit: Seems that I now have indirect access. Not sure exactly what that would mean…

5

Looks ok. Any filtering in the router for any specific territories ? Specific IP ranges ?

Would like to see if the request gets to the target machine - establish by using wireshark when doing a specific test through the public ip and port

trying http://66.211.xxx.xxx:8080/identity and seeing if it gets to 192.168.1.111

That means fallback to the Plex Relay service - see https://support.plex.tv/articles/216766168-accessing-a-server-through-relay/

6

Having the same issue since updating to 1.14.0.5468-5a0183d2c. Apologies for the larger post in advance, not trying to hijack the thread, just donate my findings since others are reporting the exact same issue I’m seeing.

I use port 49000 to forward to 32400 through my PFSense, has been solid for years until this update. Looking at the remote access page said there was an error and that it could not reach the Internet. Rebooting resolved that.

I could verify that my NAT policies were functioning correctly as I have about a dozen other services between TS3, Minecraft servers for my sons, OpenVPN servers, etc. that are all functioning normally using the same policies.

On the Network page I had to dial back secure connections to “Preferred” so I could allow insecure connection fallback.

I just ran a repair install, changed nothing as far as access. If I try to connect via HTTPS, I get the "The server “YourServer” does not allow secure connections. Clearly something with secure connections is broken as I had my secure connections settings set to required, now to preferred so I can allow insecure connections to fall back to. Not that I want to do that.

I even manually assigned the single network interface instead of Any, made no difference. I left GDM enabled even though I have hairpin NAT enabled on my PFSense. Shouldn’t matter either way and didn’t when I enabled/disabled them in testing.

Going to http://mywanip:49000/indentiy resolves with a mostly blank page that shows:

This XML file does not appear to have any style information associated with it. The document tree is shown below.

<MediaContainer size=“0” machineIdentifier=“mymachineID_removed” version=“1.14.0.5468-5a0183d2c”> </MediaContainer>

Everything I’m finding is attributing this to something in this specific Plex pass/beta upgrade. Which I guess comes with its own inherent risks. I guess for what I use on Plex, this is the buggiest or most problem ridden release I’ve experienced since going PlexPass in 2015. That’s really pretty impressive IMHO. I’m also very confident and hopeful that they’ll get this resolved sooner than later.

I am running this on a Hyper-V hosted Server 2012R2 install (up-to-date, 4 threads, 1-8GB dynamic RAM (Hyper-V host is DDR3-1600), single vNIC, Service setup to start Plex when server boots (not sure if still needed, but had working perfectly since 2015), that also acts as my home domain’s file server, print server, TeamSpeak 3 server. Again, this is the first time I’ve had this issue since going to secure required connections however long ago (years). It is odd that it wont’ accept secure connections even with it enabled. I’ve scoured all the advanced settings I could in the webGUI, not sure there’s anything to change or not internally to resolve this.

Cheers!

7

Please do not double post

Your issue is being investigated here Plex Constantly Loses Remote Access

Please add any extra info you provided here to the other forum thread when providing the diagnostics that were missing from your post there

8

Haven’t been able to install and try Wireshark yet. After a reboot from a different software installation, I tried to enable Remote Access again. As soon as I attempted this, I received an error from Ubuntu that winbindd had crashed. This (under my very simple researching) is responsible for Name Service Switch calls in C. Not sure if this part of the problem or not, just reporting what’s going on with my machine. I’m going to reboot again and see if the same thing occurs.

9

Ok. I’ve “fixed” the problem. I tried to directly access the server via @sa2000 idea of using Wireshark. When I mapped a port to PMS other than 32400 (and opened it on the router), I couldn’t directly access PMS. If I open port 32400 on the router and actually specify port 32400 in “Manually specify public port”, then Retry to map the port - it works. If I set the port to ANY other port and try to map it, no dice. Something is still amiss in the Plex backend OR in the way PMS attempts to map the port internally. Hope this helps in the meantime as the Plex team fixes this issue.

10
  1. The public port you port forward must correspond to the port number you enter in the box in server setting for remote access Manually Specify Port
  2. Some routers do not allow you to have a different port number for public/WAN and private/LAN/Local and since the local port must be 32400, for such restricted routers one would need to also have the public port as 32400. See the options you have on the Setup Port Forward screen
11

Yep. That’s what it was set like before the trouble began. I double and triple checked these settings. I also waited the prerequisite time between port changes as per your advice in another thread. Just for clarification, the only port number that works currently is 32400. I’m ok with this as I used to have to forward a different port due to an overly restrictive firewall.

Thanks, the router I’ve been issued does allow me to route ports fairly efficiently. I have many services patched through this router. Everything was working fine until these last couple of updates.

I totally appreciate the help @sa2000. We’re almost a day on now and I still have remote access!

I also noticed an update to winbindd for Ubuntu 18.04 yesterday and updated that as well. Seems like that crash was probably unrelated.

12

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