This suddenly popped up today, although I am not sure when it started (haven’t added music in a while).
I have added a couple of albums to my music directories. To my suprise they didn’t automagically show in Plex, so I went to the library and pressed the update button. It gives me:
**This server cannot reach the Internet. Please verify connectivity and try again.
Now I have been going through the forums, but somehow the fix that is proposed (removing the PubSub entries in the Preferences.xml) won’t work for me.
Some (relevant?) facts: pubsub.plex.tv resolves to 139.162.7.93 (I live in Germany)
Going to pubsub.plex.tv gives me a 403 (as expected)
Plex Version 1.0.0.2261
I can play shoutcast through my plex interface, so the server should be able to connect to the internet.
Just to make it complete: I run plex in a docker environment. Updating the music library has worked in the past, so this configuration should not be the issue (although one never knows).
The server asks plex.tv for a list of pubsub servers and does a test connection to each and then picks up the fastest connection pubsub server.
Could you enable debug logging and restart the server, Wait 10 minutes and then try to update a premium music library and if it fails please attach the full Plex Media Server.log
On a, possible, related note: since I have upgraded to version 1.x of Plex Server, plex web tells me the server is not connected to the internet. Which is not true, since I can connect through the cell network without an issue and I do see “others” watching content as well. Not completely sure when this started, since I don’t check the server settings on a regular base. Normally plex just works ™.
Please could you repeat what was done earlier and send me a new log file and I will re-open the issue I raised to get it re-investigated. Please follow same steps as before
Thinking about the issue. I think it all started when my cable modem broke down. As a temporary solution I got a device that forced me into double NAT mode, thus removing some of the functionality I had. During those days Plex was accessible from outside my network, but I couldn’t reach it at home.
My modem is now replaced, so I am back to the original situation again (no double NAT anymore). It seems as if the server never recovered from that situation though.
I hope you don’t mind me jumping in on this but I have been having the same issue since 3-4 Plex versions ago, I have pm’d you my log file.
Many Thanks
For some reason getting 403 errors from pubsub.plex.tv servers to requests from your server.
Do you have any special security / firewall software that may be blocking requests to any of these IP Addresses ?
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 82.94.168.55 was 5 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 82.94.168.52 was 6 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 139.162.245.220 was 21 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 139.162.144.200 was 27 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 173.255.237.43 was 156 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 45.79.211.86 was 186 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 65.52.235.203 was 215 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 45.33.118.95 was 270 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 173.255.253.36 was 311 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 139.162.7.93 was 507 ms.
Apr 07, 2017 09:01:53.624 [0x7f3fccffe700] DEBUG - PubSubManager: Time to connect to 139.162.117.249 was 538 ms.
thanks for your time, here is the response from my VPS provider, hopefully it will help!
"The forum post is not applicable on our situation, we are not using Nginx or any web server in front of Plex. "
Many Thanks
Thanks. Will need to get this looked into to see why the requests are being rejected - as Forbidden.
So will need to look at the tokens that are being used.
Could you repeat the test as before after enabling logging of tokens (server / settings / general / show advanced) and also enable verbose logging as well - so debug + verbose + token logging.
Then restart the server
and reproduce the issue as before and send me the Plex Media Server.log by private message
Could you also do a request in a browser and save the returned xml into text file and send it to me
The request is https://plex.tv/servers/c903bb70ff11ef16996f023aa7129a89b76fc7ae/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
You will need to replace the xxxxxxxxxxxxxxxxxx characters with an actual token for your server
You can find out what that is from the Preferences.xml file - item PlexOnlineToken
Location of Preferences.xml is /var/lib/plexmediaserver/Library/Application Support/Plex Media Server/Preferences.xml
That requests lists your tokens - please copy to text file and send me by private message together with the log
@mbcplexserver not sure where you got to with this - but an issue has been identified with servers hosted with bytesized hosting where tokens used by the server are not ones obtained by the server.
