From my location the “United States” and “Ireland” regions should not be blocked. Plex appears to have their data centers in these locations. I have all other regions blocked and remote access status is green and working.
So this should be a good starting point for anyone else have similar issues and suspect GeoIP blocking may be the cause…
.
I am having the same issue, since this morning. Fixed local IP, port 32400 open, but I keep getting " Not available outside your network".
To be precise, if i keep disabling and then re-enabling it, eventually it will become green, stay so for some 15 seconds, and then spontaneously go red again.
The red X is only between “Internet” and my public IP, the other always shows fine.
What is going on!? Not only does Plex say that it’s not available outside the network but it IS available. But that’s not the concerning part. When I turn off remote access I STILL have remote access even after disabling remote access, UPnP, and port forwarding. This is very concerning.
When Remote Access is enabled connectivity tests are made and events generated and passed to the server. These would come from the Amazon AWS servers and Amazon do publish a list of all their IP addresses which do change from time to time. In addition to the AWS servers, geographically aligned pubsub servers are currently used and again the IP addresses of these may change. The list of pubsub servers can be seen by making this request https://plex.tv/services/pubsub/servers - the results returned may vary from one request to another
According to plex.tv held information for your XPS 15 server the public port you have for remote access is not 32400 - so presumably you are using the dynamically assigned uPnP mapped port instead of manually specify port ticked and 32400 entered to correspond to the port forward in the router for public port 32400
That’s because in order to make it work i kept enabling and disabling, and also forcing or not forcing port 32400. Right now, for example, this is the situation. And it keeps happening at random times.
So at the time of the screenshot, was there a port forward in the router to forward public tcp port 32400 to local port 32400 to 192.168.1.15 ?
Could have a look at logs from the server after a restart and with debug logging enabled and also screenshots of the port forward in the router
Web Client Debug enabled. Router Screenshot.
Now it shows as accessible. But it comes and goes without me touching any setting…
Port Forward looks ok. Was it always in place?
Would be interested in the server logs not the web log
See https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
When the problem arises please check port 32400 with canyouseeme.org and also confirm that the port forward is still in place in the router and collect the server logs and attach the zip here. By the way you can attach images in posts as well - so no need for them to be uploaded elsewhere
Please test out the remote access by attempting to access the server, eg through cellular with wifi disabled on mobile plex app
When providing logs/screenshots please indicate when you noticed the problem and confirm if server was accessible or not
Thanks
Oops, yes server logs were always enabled. And yes, the Router rule was set months ago and never touched.
OK, I’ll do as you said and post logs/screenshots next time the problem occurs.
Thank you!
Same remote access trouble. I roll back PMS this evening to 1.13.2.5142 and everything is fine again.
I think I may have found a bug that I can trigger so I thought I’d post here to help diagnose the problem.
Remote access drops randomly and frequently. But last night I think I triggered a bug. I opened PMS dashboard to see what my brother was watching. This caused PMS to cut remote access. This happen last week to another family member but I wasn’t sure if I had caused the drop.
Below are two sets of logs taken soon after PMS dropped remote access.
The only thing I did was open PMS in Chrome, click on activity and select dashboard. The Remote access link broke straight away each time.
Plex Media Server Logs_2018-12-30_23-51-55.zip (2.9 MB)
Plex Media Server Logs_2019-01-04_23-02-57.zip (3.8 MB)
Unfortunately, my situation isn’t even this good. I cannot get my PMS to successfully enable remote access. Ironically, it only affects MY server. The servers of friends who I’m sharing libraries with – I can get their files just fine, thank you very much.
Tonight, I sat down and using TWO computers, so I wouldn’t have to do that annoying screen flip – and also, printing out a hard copy of my browser’s Operating Manual (all 105 pages) – I set out to fix this.
Did everything, Static IP, recorded the MAC address, manual port forward. Took about two hours. But, still not remote access. The problem is in the Public address.
Now, I have a question – since we have to ‘freeze’ the IP address for our private networks, why is that not an issue for the public ones?
I can assign a port, but I cannot make sure that the public network always has the same IP address? So, if that’s such a huge deal for the private network, why isn’t it similarly one for the public settings? Don’t those pieces of software function essentially the same way? I’m not an expert, just using logic.
I will wait for few days to hear back before trying the idea of rolling back the version. Although, I have found that notion gets much more traction, and over many more apps than it should (Are you listening, Skype?)
Plex Remote Access (Not available outside your network even when enabled)
Hi I am having exactly the same issue Im running Version 1.14.1.5488 (as of today 06/01/19) cant remember when I last updated though!
I run PMS on a Dell R510, running Windows 2012R2 and it has been working fine since install a few years ago, I use Plex Pass to access remotely and use apps on my Iphone, Ipad and TVs to access it and it works as expected (friends of mine also access it from their homes via Ipads using the app and a plex pass!
The other day I added a few new films to the library and all was fine until I decided to watch them and my TV couldnt find the service (if this happens in the past its because the server has re-booted and Plex has not restarted as it should, easily solved).
Anyway (sorry if this is a long winded post!)
So now I have noticed that Remote access does not seem to work consistently.
The firewalls on the server are disable (temporarily to rule them out) and my Router is and Asus RT87 niehter of these have been changed so it cant be a setting on these (i disabled the FW on the router also as a test and still no joy)
Server has a reserved static IP address internally always has and never needed to set up a port forwarding on this server as it work straight out of the box)
What I have noticed is that when Remote access is enabled and appears to be working the minute I try and access it via either a browser directly on my PC (directly to the server IP and port) it seems to then break the connection to plex where it then says not avialbe outisde my network however remote access is still enabled (but the private IP and public IP are not populated!)
I am figuring that maybe trying to access it remotely kills the connection! What is wierd is when this happens I can find the server locally on my network either, my TV’s IP and networks are list to allow access without auth too!
I just dont get it I think the remote access issue of disableing itself isnt maybe a fault but is maybe triggered by a device trying to access it and what ever happens it then causes the remote access on the PMS to fail but still shows the staus of remote access enable even though its not avaialbe!
Any help greatly appreciated (on another note when trying to disable remote access after failure the connecting server seems to take ages!
Cheers Guys
Log attached (or they should be!)
Plex Media Server Logs_2019-01-06_12-28-35.zip (2.4 MB)
We fix the private IP Address because if using a manually selected port and a port forward we define in the router where the port forward goes to. If the local IP address changes then the forwarded port will no longer get to the right device (the server)
If not using manually specified port and instead using the automatic uPnP configuring of port then it need not be fixed
However - any change in IP address whether public or private will give to rise to temporary interruption as the route to the server would need to be communicated to plex.tv and the plex client apps get the updated information from plex.tv
Plex TV is acting like a dns service basically as PMS is logged into the plex TV account it will update your external IP address.
Still doesnt help my issue though (im rolling back to the previous version to see if it makes any difference!) not really sure what has change as it has been working on this version up until a few day ago!
I have been having this problem for several months. Here are my download logs.
Plex Media Server Logs_2019-01-06_15-46-41.zip (6.0 MB)
i can’t see that in the log - well, not happening after you look at the bandwidth chart
Looking at the 2nd zip file - for 3rd and 4th January, I can see that bandwidth statistics were requested from the server at 22:53:25 on 4th Jan.
But there network issues before that - with the network interface going down a number of times and at times when no bandwidth dashboard staticstics were being requested
The network interface on the PC went down at these times
Throughout this period DNS was down and so all attempts to communicate with plex.tv were failing - see curl error 6
went down 22:52 on the 4th jan for a few seconds
went down 22:54 to 23:02 on 4th jan
I will have a look at the other set of logs - but at this moment there is no evidence that it was related to the bandwidth dashboard view.
I have looked at the logs from the 30th December. The dashboard bandwidth data was being requested between 21:24 and 23:40 on the 30th. After this you disablled and re-enabled remote access at 23:41. A connectivity test immediately before this at 23:40:55 was actually successful and reached the server - it was at that time through uPnP public port 15632 - so there was no reason to disable and re-enable remote access. I see you switched to manually specified port 32400 at this point - it was not before that
What made you think remote access was down ? The oldest log entry was for 21:21 pm on 30th. You were already watching the bandwidth chart - so if something went wrong as you started - it was before the beginning of the oldest log file. You have verbose logging enabled - suggest you switch it off and instead ensure debug logging is enabled - verbose server logging is only needed for specific investigations. With debug only, hopefully the logs would cover the time when remote access apparently drops off
If you could try again without verbose logging and with debug logging and when you think it dropped off, try with a mobile device with wifi disabled
.
Thanks for all the detail.
I need to see the logs when Plex Media Server made a connection to the Pubsub server = this is a machine that get used for connectivity testing and raising events to Plex Media Server. I can see that the server failed to get an event for the connecitivity tests at 10:47 on january 6. Also at 12:23 and 12:25
I see that you are running Plex Media Server as a service or scheduled task. Of course there would be a risk of it running another process outside the service - This can arise if you use a different windows account for install - different from the account the service runs under
I need to establish which pubsub server the Plex Media Server is using for the events. Unfortunately the period of time covered by the logs does not show any connections to pubsub servers. You have verbose logging enabled and that fills up logs very quickly. For this type of issue, debug logging is all that is needed - see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
May be there was an issue establishing the connection to the pubsub server - you mentioned firewall off. Is there anything that may be blocking the connections to these servers = the pubsub servers ?
So could you disable verbose logging in server general settings and ensure debug logging is enabled. Restart the server, wait 10 minutes and then capture the logs. Confirm that remote access works. Then when you have the problem, confirm it is down by attempting access through a mobile device with wifii disabled. Note down the time so you can mention it here and capture the server logs and screenshots of the remote access setting page. and attach here
Then go through disable / re-enable remote access. and if there is an issue,. refresh the browser with F5 and again capture logs and screenshots
Do you have any software that may be blocking some IP Addresses ( some geo blocking ) ?
Thanks for providing the logs.
The logs you are using the default automatic configuration of remote access through a dynamically allocated uPnP port.
Each attempt to get the router map a port is failing
Jan 05, 2019 16:23:27.337 [13248] DEBUG - NAT: UPnP, attempting port mapping.
Jan 05, 2019 16:23:27.399 [13248] WARN - NAT: UPnP, error mapping port 17133, error: Action Failed, controlURL: http://192.168.1.223:5555/ctl/IPConn.
Jan 05, 2019 16:25:06.128 [11956] DEBUG - NAT: UPnP, attempting port mapping.
Jan 05, 2019 16:25:06.183 [11956] WARN - NAT: UPnP, error mapping port 28811, error: Action Failed, controlURL: http://192.168.1.223:5555/ctl/IPConn.
Jan 05, 2019 16:25:09.933 [1328] DEBUG - NAT: UPnP, attempting port mapping.
Jan 05, 2019 16:25:10.018 [1328] WARN - NAT: UPnP, error mapping port 24969, error: Action Failed, controlURL: http://192.168.1.223:5555/ctl/IPConn.
Jan 05, 2019 16:26:52.937 [0876] DEBUG - NAT: UPnP, attempting port mapping.
Jan 05, 2019 16:26:52.997 [0876] WARN - NAT: UPnP, error mapping port 18830, error: Action Failed, controlURL: http://192.168.1.223:5555/ctl/IPConn.
Jan 05, 2019 16:27:15.128 [11968] DEBUG - NAT: UPnP, attempting port mapping.
Jan 05, 2019 16:27:15.193 [11968] WARN - NAT: UPnP, error mapping port 17417, error: Action Failed, controlURL: http://192.168.1.223:5555/ctl/IPConn.
Jan 06, 2019 15:36:15.575 [18224] DEBUG - NAT: UPnP, attempting port mapping.
Jan 06, 2019 15:36:15.575 [18224] DEBUG - NAT: UPnP, didn't find usable IGD.
Jan 06, 2019 15:36:15.575 [18224] DEBUG - PublicAddressManager: Mapping failed.
Check that NAT / uPnP are enabled in the router
It may be that the router got into a state where it needs to be rebooted
If problem persists and disabling / re-enabling remote access does not succeed in getting a port mapped, get some wireshark packet capture to go with the logs. Download wireshark link Wireshark · Download
Save the wireshark capture to default pcap file and zip and send me by private message and provide logs as before
If automatic port mapping continues to fail, consider switching to having a port forward setup in the router and selecting manually specify port
