DM’d you the logs.
I’m seeing this is a well. Started seeing PlexPy / Tautulli “ping-ponging” Plex Remote Access failures yesterday morning. Going on all day yesterday. Despite the Tautulli failures, remote access worked yesterday the few times I tested it. Today, remote access to the server has started failing randomly for users. I’ve turned off Tautulli for now in case the repeated checks are interfering. Remote access is still flaky today. Shows as as working on the server, then shows as failing, then shows as working again. I’ve tried disconnecting and re-connecting the server to my account, too.
I think Tautulli is not the issue, but showing that there is a connection issue regarding Plex. Is everyone that is have this issue on 1.13.5.5291? I think the first thing is to see if it is the update that started it or something with the Plex authentication servers or something else all together.
Indeed I’m on 5291. Not sure I remember when I actually last updated. Could be quite recent.
Mine started the second I updated.
I have looked at the logs from 29th july (period covered 14:26 to 14:54)
They show timeouts on requests to plex.tv and one of the requests that timed out was one relating to the information for remote access and the port used
There was no outage of plex.tv for this duration so my thoughts are that it may be a network issue at your end / could be router issue / ISP issue
This shows a selection of the requests made during the period and those that timed out
This just spontaneously resolved itself the next day. Looks like a potential routing or ISP issue, rather than anything else.
I’m having the same issue and I’m on 5291.
Same issue, 
I had a similar issue where Plex could not be reached from the Internet. In my case it seems to have been router firmware update. I have Netgear R6300v2 which updated to firmware V1.0.4.28_10.0.89 and Remote Access quit. It did not appear the firmware update changed any setting yet Remote Access no longer worked. I reinstalled the previous router firmware V1.0.4.24_10.0.87 and everything worked again.
If you have an issue please provide diagnostics or a link to a post where you have attached the diagnostics
What would be needed are logs with debug logging enabled beforehand and covering time when remote access starts to fail
If you are using uPnP auto port mapping in Plex Media Server, you should consider switching to a port forward in the router and using the manually specify port option in server setting and entering the public port mapped to the server local ip address
For logs see
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Hello,
I was just setting up Plex remote access as well having spent a good part of the weekend on this. After reading through a bunch of threads and confirming that ports are mapped correctly Plex shows as available but the logs are full of these types of errors:
Sep 01, 2018 22:38:02.366 [5624] ERROR - Error parsing content.
Sep 01, 2018 22:38:02.366 [5624] ERROR - Error parsing XML.
Sep 01, 2018 22:38:02.366 [6088] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:02.366 [6088] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Sep 01, 2018 22:38:02.366 [6088] ERROR - Error parsing content.
Sep 01, 2018 22:38:02.366 [6088] ERROR - Error parsing XML.
Sep 01, 2018 22:38:02.366 [5744] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:02.366 [5744] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Sep 01, 2018 22:38:02.366 [5744] ERROR - Error parsing content.
Sep 01, 2018 22:38:02.366 [5744] ERROR - Error parsing XML.
Sep 01, 2018 22:38:05.474 [5536] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:05.474 [5536] WARN - HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Sep 01, 2018 22:38:05.474 [5536] ERROR - Error parsing content.
Sep 01, 2018 22:38:05.474 [5536] ERROR - Error parsing XML.
Sep 01, 2018 22:38:05.474 [6964] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:05.474 [1504] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:05.474 [6964] WARN - HTTP error requesting GET https://plex.tv/users/account.xml?auth_token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
Sep 01, 2018 22:38:05.474 [1504] WARN - HTTP error requesting GET http://plex.tv/pms/:/ip (0, No error) (Could not resolve host: plex.tv)
Sep 01, 2018 22:38:05.474 [1504] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):
Sep 01, 2018 22:38:05.489 [6964] ERROR - Error issuing curl_easy_perform(handle): 6
Sep 01, 2018 22:38:05.489 [6964] WARN - HTTP error requesting GET https://plex.tv/api/v2/user/privacy?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (0, No error) (Could not resolve host: plex.tv)
I’ve attached the full log here. If anyone can tell me whether this is related to a current Plex issue or a configuration problem on my end I’d appreciate it.
com.plexapp.system.log (943.4 KB)
curl error 6 is DNS error
Check that you have internet connection on the server and DNS is working
Also ensure debug logging is enabled
see https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
and restart the server after enabling it
and the logs are obtained as explained here
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
Interestingly I have the “Not available outside your network” message, but I can get in just fine from the iOS app as well as browser. So everything is working, but would like the incorrect error message to be remediated.
Hi @sa2000
I’ve taken the steps as outlined in your links to configure logging to debug rather than verbose.
The server is has connection and DNS is working fine
Port forwarding is configured and static IP lease set correctly.:
What I don’t get is why I see available and then again not available. It’s switching on and off which it wasn’t doing before.
Server Version 1.13.5.5332 (Win 10 x64)
I’ve attached logs, if you can specify which specific logs I should upload in the future I’ll separate the chaff from the wheat.
yes - the log no longer shows a DNS issue
I don;t understand your router port forward - the port number looks wrong and it looks to me back to front
what router make / model is this?
The port should be 32400
32400 is the Destination Port(s) and not the Source Port(s)
Source Port(s) i would assume to mean the source port on the request which would by any.
and Source zone should be wan and destination zone should be LAN
and Source IP Address should be ANY and Destination IP should be the connected server on 192.168.1.204
Thank you!
I’m really confused now. My iOS app is now not connecting, but I can get in via browser.
I’m assuming this is tied to me migrating my PMS setup from one machine to another using the same PMS name (same source/target OS).
try signing out and in on the clients
