Thanks for the logs which showed failure to connect from the outside to your server on port 443 and public IP 188.25.xxx.xxx at 14:08 on 11 May
Could you get me screenshots from your router please for DHCP Reservation for the server on 192.168.0.6 and the port forward screenshot for tcp port 443 to 32400 for 192.168.0.6
Also please tell me what security software / firewall you have running
Also please let me know if the WAN IP address you see on canyouseeme.org is the one starting with 188.25.xxx.xxx and if that is the same WAN/Internet IP address showing on the router WAN/Internet status page
I highly doubt that it’s a port forwarding issue - 443 is the standard SSL port so HTTPS connectivity wouldn’t work if it wasn’t accessible.
I’d also reiterate that there were no networking changes (in router configs or otherwise), and that the problem started with the upgrade to the current version of PMS, which likely isolates the cause to new code that might have broken it.
On the details you’ve requested, here are screenshots of the virtual server config on my router (the configs for port forwarding are identical), as well as my DHCP reservation for the machine that’s hosting PMS.
On security software - there’s none installed, aside from UFW, which is the default firewall on Ubuntu - it’s configured to allow both ports properly and I haven’t had any problems until (again), the upgrade.
canyouseeme doesn’t see port 443, but that website is barely an indicator of connectivity, as there are multiple ways to obfuscate open ports to scans from outside the NAT, even if under normal circumstances there are services properly running on them.
i watched the Problem some days and talk to other People about this Bug.
My problem is: i cant reproduce this.
But in generall, i not longer think, it’s a Plex web Bug, it’s a Serverside Issue.
It’s not only happened at Plex web. Some users with the Plex app on android also have Problems. Suddenly the Server disconnects and after a minute or so the server is back.
which results in skip the actuall Song a Plex web and play the next one if the server is reachable. I have this issue often if i stream with mobile data at Plex for Android and have a bad Internet connection.
But at this bug, i noticed it on different DSL connections. Suddenly the Server is gone and after a short time (this can be seconds to 1-2 minutes) he is back.
i try to get clean logs in the next Days. (some days its working and some days i ihave this issue 3-4 times an hour)
Having same problem,Ran well for many years,Now overnight,i now get the no direct connection and only get indirect access which is limited to 2mb,
Not touvhed anything or installed anything,Had plex pass for a while now ,Tried reinstalling ,deleted all hidden files,turned off all Virus,Firewalls ect… but still the same
Noticed every now and then it turns green for maybe 5 secs then go back to red,Also console option on plex settings seems to be coming up with a few errors connecting
The newest version of PMS doesn’t solve the problem. Any idea when the devs will start looking into this seriously? Remote play has been broken for two versions now.
I have lately noticed a bug where if you don’t specify the port manually, it searches on port 0 for incoming connections instead of the hard-coded default of 32400. For anyone without networking and server knowledge, port 0 does not exist. It’s a bug in the Plex software.
Simple fix, just select the button and specify 32400 or whatever you’re forwarding to. Don’t reply on uPnP, that technology is a wonderful concept but has it’s quirks as most things dynamic tend to.
Yes that’s exactly correct. It’s like listening on the ip address 0.0.0.0 which translates in Linux systems to listen on all active links. Plex really doesn’t seem to be able to handle this, and since it’s only for special use cases, connectivity fails.
If I allow Plex to try to listen on port 0 I lose all remote connectivity.
Says the guy who threw the first stone.
I’m only trying to help others. I’m more than qualified. You take offense to it and that’s your prerogative, but your derogatory comments don’t contribute to the greater good and aren’t necessary.
I agree Duvazh, “rsava” I was always told if you have nothing nice to say don’t say anything at all, why would you even start that, what because he sent you his credentials? I work for the Federal Government in IT and in the IT world you always need a fresh perspective. The guy is simply offering free advice and you disrespect him, no wonder he was offended.
Exactly the same here, very frustrating those no direct connections. Problem is a can’t reproduce this problem to provide logs like requested in this topic… Sometimes it’s good for hours and sometimes the connection is gone!
I just for giggles created another inbound rule in Windows Firewall to allow port 32400 (my port choice) and am crossing my fingers, so far it is working. What I noticed when going through the inbound rules is despite explicitly using 32400 I saw nothing in any of the Plex rules that explicitly opened that port 100% inbound. If this worked for you please let me know. What concerns me is IF this is the problem why isn’t it fixed with a newer build?
UPDATE: I run two servers, my main server, the one I use primarily for everything is running fine about 98% of the time. This dropout started when I started the post roughly two plus weeks ago. My experience with this dropout issue is random and doesn’t happen very often on my main server but still happens nonetheless (still trying to figure this one out). For this server I have attached the server logs. Plex Media Server Logs_2019-05-22_15-19-29.zip (3.4 MB)
My other server is much different, this server is my backup server / test server. Side note both servers run on Windows 10 and have almost an identical system setup. I use my second server as a test server before I run something on my main. The issue with the test server is severe, it has no “Remote Access” at all. When I mess around with it, all firewalls and VPNs off and setting everything from the port forward to none to testing different ports to turning the setting (Remote Access) on and off in PLEX the result is always the same, I get about 5 seconds of a green check mark then it goes red and I have no remote access. In the past I was able to fix this by just running the VPN bypass scripts and restarting, but this no longer works.
More observations with the test server issue: I also run PIA (Private Internet Access) on both servers using their UI program to connect. I have noticed that since PIA has updated their software (a few weeks ago) that something is up but only on my test server, the main server is seemingly unaffected by this update. It’s also worth noting that one of the differences between servers is that my main server runs PIA UI 1.1.1 (stable version) and my test server now runs a beta version of 1.2. I have tried both versions of PIA as well as other versions of the new software and I get the same results on my test server, same issue persists. Even though I run scripts to have PLEX bypass my VPN, for some reason the PIA software is now interrupting PLEX’s “Remote Access”, essentially overriding PLEX and causing PLEX to report “no internet” creating the disconnect. If I turn off PIA then PLEX’s “Remote Access” will turn green and I have access again. So, it seems to me that PIA may be the real issue here.
As you can see I now have two separate issue, both involving PLEX’s “Remote Access”. As for the original issue of seemingly random “Remote Access” dropouts involving my main server, I still have zero ideas as to why this is happening, but it is, STILL. And, for the second issue on my test server, I no longer feel like this is a PLEX issue. I think this issue is due to PIA’s new software update and how that program handles the DNS/IP info, however I’m not 100% sure on this and still would like to fix this or find a work around that is suitable to my needs.
Finally, I attached my logs for my main server up at the top of this post. I experienced the “Remote Access” dropout at 3:08pm then “Remote Access” came back up at 3:18pm. Hopefully these times will help cut down the search for something going on. I looked at the logs but admittedly I don’t really know what I’m looking for so here you go anyone who wants a crack at it. Thanks. Sorry for the novel, lol.
