Interesting - with the 256 number of mappings, I thought it would be the other way round
Would like too see logs of it working in this way
right, i did too!
maybe if I check it again, and then delete all 256 mappings, it may start working properly again…
Agree/
Let me know more I can provide to aid in troubleshooting. Here in Austin I continue to connect to the DFW POP I mentioned- and it continues to report my server offline after several hours.
would need to see debug server logs for when it transitions from available to offline
Is the pubsub02.pop.dfw.plex.bz server sending events periodically to the Plex Media Server? Is it sending an event when a connectivity test is attempted ? Need to see the logs
https://support.plex.tv/articles/201643703-reporting-issues-with-plex-media-server/
https://support.plex.tv/articles/200250417-plex-media-server-log-files/
If you are looking for pubsub related problems, then perhaps you should take a look at mind. I feel like the cause is a hundred percent due to the pubsub servers.
I have manually port forwarded 3400 from my router.
Plex is 100% reachable from outside of the network. From remote locations, if I visit the public ip address then I can access the server and watch anything I want.
However, through plex.tv the server is only reachable as an “indirect” connection.
I have tried manually adding the ip addresses (including a duckdns url) to the network settings for a custom url with no change. Again. I can 100% access plex from outside my network, but plex does not correctly publish my server.
Plex Media Server Logs_2019-02-09_15-04-39.zip (3.2 MB)
I have tried forwarding a different port, downgrading and completely reinstalling plex and disabling secure connections. Nothing has resolved this issue.
I unchecked that UPnp setting nearly two years ago and my remote access has been rock solid ever since. I posted my findings here:
1 Like
I am seeing communications with plex.tv failing as from 14:04 on 9 Feb. Did you configure some routing ? proxy? plex.tv requests from the Plex Media Server are going to plex.tv on port 9050 as from that time.
Extract showing the changeover
Successful communication
Feb 09, 2019 13:52:04.441 [3740] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=987b8d2b-8a62-4d07-ae62-99b9d9ab7553
Feb 09, 2019 13:54:03.571 [8124] DEBUG - HTTP 201 response from POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=dc4b516f-ff39-433c-9c49-709e58c183ec
Feb 09, 2019 13:54:04.950 [3036] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=b3e81ef1-2bb7-46b9-892c-335ebe4bff50
Feb 09, 2019 13:54:05.991 [3320] DEBUG - HTTP 200 response from PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=36edf0fc-8a60-4059-a06f-ce96a510e59e
and ftom this time all requests to plex.tv bounced because for some reason they switched to tcp port 9050
Feb 09, 2019 14:04:29.285 [7432] WARN - HTTP error requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=4a4de1f1-86a0-431f-b52b-c19e7ff4c336 (0, No error) (Failed connect to plex.tv:9050; No error)
Feb 09, 2019 14:04:31.296 [9204] WARN - HTTP error requesting PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=690ca8d1-6292-4474-b156-50d7a7382b8f (0, No error) (Failed connect to plex.tv:9050; No error)
Feb 09, 2019 14:04:33.298 [3716] WARN - HTTP error requesting PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=08167a3c-24dd-4921-a370-5c12db31915b (0, No error) (Failed connect to plex.tv:9050; No error)
Feb 09, 2019 14:04:35.300 [10216] WARN - HTTP error requesting PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=1436344f-035b-4d61-9607-dc835f1c9eab (0, No error) (Failed connect to plex.tv:9050; No error)
Feb 09, 2019 14:04:43.540 [7540] WARN - HTTP error requesting POST https://plex.tv/servers.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&async=1&asyncIdentifier=a0c9efb1-3858-4314-8e40-cbbfe28a1f85 (0, No error) (Failed connect to plex.tv:9050; No error)
Feb 09, 2019 14:04:45.552 [10216] WARN - HTTP error requesting PUT https://plex.tv/api/servers/6b9e6cd9203729871f54f30116b6b0ca9689c547/connectivity?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx&asyncIdentifier=dfa788d8-28bd-44e4-a8b1-751439642b1e (0, No error) (Failed connect to plex.tv:9050; No error)
Did you do anything on the network ? start using a proxy ?
I did not do anything on the network.
I do not have a proxy or a VPN running. (There is a VPN that runs on a docker host, but that should be isolated and as troubleshooting steps, I shut that down completely a while ago).
There were no changes made to the network at all between those to posts. I don’t know why plex is choosing to use 9050. I will run a packet capture shortly here.
I have PM’ed you a wireshark capture.
Thanks - Most are not showing up in wireshark.
All the https requests were failing.
http was ok.
Could you try this with curl
`curl “https://plex.tv/services/pubsub/servers?X-Plex-Token=xxxxxxxxxxx”
You need to put in the the server token - see https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
You can download curl binary for windows curl - Download
Let me see what you get back. You can send by PM
Further to my earlier post, could you also to save the Windows System and Application event logs into evtx files (using eventvwr.exe) and send them to me zipped by Private Message. Also note down the first event or last event date/time for each as i may need to adjust times due to potential timezone differences between us
I would like to see if there are any clues there as to what changed on your PC between 13:54 and 14:04 on February 9th.
I am also having the same issue. I had Plex running smoothly on my desktop and HTPC a week ago. I then rebuilt my HTPC and reinstalled Plex, now I get horrible buffering and loss of remote access. I’ve included my logs. I have both ports forwarded , and PLex is excempted in my Bitdefender Firewall settings. ANy advice would be welcomed. ThanksHOME Plex Media Server Logs_2019-04-05_21-40-37.zip (4.1 MB)
HTPC Plex Media Server Logs_2019-04-05_21-41-09.zip (3.2 MB)
I had no problems for almost a year (only counting that far back as I changed internet providers at that time) until the last couple of server updates. Now I have to retry or re-enable remote access multiple times each day.
Don’t want to just throw logs at you. Was there a “here’s where to start” as to giving the most useful data?
2 Likes
I’m also having this issue. Dunno how to fix it. I tried port forwarding and it still turns on and off. Will they fix it ? I have a VPN installed on my pc but it’s not active when I try to connect
Hi,
Have you guys happened to read Part C) of the following guide? There are a lot of Remote Access problems fixed, listed here
I’ve tried ALL of that. even when Plex says I’m not externally visible, all of the other tools say I am. A retry might make me visible for seconds or hours. It comes and goes, seemingly at random and I have only had the issue for a couple of months. Something must have changed, whether it was in Plex or my network, but there have been no changes in my network as far as I can tell. In my mind, the fact that simply disabling and enabling remote access can bring it back online for a period of time makes me think the issue is software related.
I’m just about at the end of my rope here, which is sad since I’ve been on Plex for something like 4 or 5 years. I may just have to look for a “not so bad” alternative that can actually stay working when I’m travelling.
I’m now getting similar behavior after just installing the latest update (1.15.3.876). I’ve had remote access working fine for years. Now it says “not accessible”. If I click on “retry” it checks, says it’s fully accessible, and then a few seconds later, it changes to “not accessible”. Retry, on, few seconds off. I haven’t checked whether it is in fact accessible outside the network (as I’m not outside the network…)
I’ve fiddled with my port forwarding. I’ve fiddled with almost innumerable combinations of manually specifying ports, not manually, etc. ,etc.
What’s a definitive guide to tracking down the issue?
1 Like
I’m having the same problem Video playback buffering and remote network keeps dropping out
Iv tried turning off firewall and everything else my remote access into the sever works fine but the Plex sever fails.
Hi to @clwill,
Yes I too am aware that Plex Remote Access tends to list “not accessible” at times on the Plex web server page. I too sometimes experience this listing, and this may be a bug with a recent PMS update. However this “not accessible” listing may not actually be a true representation of a steady remote access connection. My remote access has been working fine ever since applying the fixes that are listed in the above guide link, even if Plex shows Remote Access as being down.
If anyone continues to see this happen, try remotely connecting to your server (eg via your phone’s 4G internet) and then playing something when it states as being “not accessible”. This may then prove that its not actually down.
