Can't update my premium music library, " This server cannot reach the Internet"

General Discussions
21

@orlando08 said:

@sa2000 said:

@orlando08 said:
Thanks but i can’t find PubSubServerPing and PubSubServer.
I have plexmediaserver on linux mint.

What is in your Preferences.xml ?

I said before, i can’t find PubServer … but after i discovered that it is inside of Preferences.xml.
I guess I have to delete the entire line is:
PubSubServerPing=“75.412800000000004” PubSubServer=“194.109.153.214”

The support page i linked which i said tells you where the data items are has the following text note

Linux
In Linux, the Preferences.xml file in the main Plex Media Server data directory contains the corresponding settings.

and I did no say PubServer but PubSubServer

So the answer is Yes - you delete those two lines in your Preferences.xml

PubSubServerPing="75.412800000000004"
PubSubServer="194.109.153.214"
22

I did.
Thanks.

23

thanks this was the solution for me to update music.

24

i tried it but unfortunatelly had no luck - got the same error message when i tried to update my music section

25

@McLovin. said:
i tried it but unfortunatelly had no luck - got the same error message when i tried to update my music section

Tried which option? Versions 0.9.14.6 and 0.9.15.0 have the fix.

Enable Debug Logging & Restart Server. Wait 5 minutes. If unable to update premium music library, take screenshot (shows time of error) and get the Plex Media Server.log and attach both here using Attach image/file button

26

I am running version 0.9.15.0 but still got the error. I enabled the Debug Logging as you suggested - unfortunatelly there is no time mentioned on the error message (see attached). But i turn of the server after i got the error so it should be one of the last entries in the log.
Many thanks for you support!

27

@McLovin. said:
I am running version 0.9.15.0 but still got the error. I enabled the Debug Logging as you suggested - unfortunatelly there is no time mentioned on the error message (see attached). But i turn of the server after i got the error so it should be one of the last entries in the log.
Many thanks for you support!

The log does show a problem with the communication with the pubub.plex.tv server selected from the list. Plex Media Server gets a list of IP Addresses for the pubsub.plex.tv and tries all. Initially it would use the one previously selected and remembered in the registry.

Could you first check that it is not your firewall that is terminating these communications.

The connections were to the IP Address showing in these extracts

Jan 11, 2016 16:23:56:291 [11384] DEBUG - EventSource: Connecting to 82.94.168.11
Jan 11, 2016 16:23:56:291 [8880] DEBUG - EventSource: Resolved to 82.94.168.11
Jan 11, 2016 16:23:56:318 [5716] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 11, 2016 16:23:56:318 [5716] ERROR - EventSource: Retrying in 15 seconds.

Jan 11, 2016 16:24:11:315 [8880] DEBUG - EventSource: Connecting to 82.94.168.11
Jan 11, 2016 16:24:11:315 [8880] DEBUG - EventSource: Resolved to 82.94.168.11
Jan 11, 2016 16:24:11:354 [5716] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 11, 2016 16:24:11:354 [5716] ERROR - EventSource: Retrying in 30 seconds.

Jan 11, 2016 16:24:41:359 [5716] DEBUG - EventSource: Connecting to 82.94.168.11
Jan 11, 2016 16:24:41:359 [5716] DEBUG - EventSource: Resolved to 82.94.168.11
Jan 11, 2016 16:24:41:385 [8880] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 11, 2016 16:24:41:385 [8880] ERROR - EventSource: Retrying in 60 seconds.

Jan 11, 2016 16:25:41:374 [8880] DEBUG - EventSource: Connecting to 82.94.168.11
Jan 11, 2016 16:25:41:374 [8880] DEBUG - EventSource: Resolved to 82.94.168.11
Jan 11, 2016 16:25:41:403 [5716] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 11, 2016 16:25:41:403 [5716] ERROR - EventSource: Retrying in 120 seconds.

The connection test timings were as showing below

Jan 11, 2016 16:24:10:706 [7216] DEBUG - Pinger: Connection test to 82.94.168.15: min/avg/max: 27.1/29.3/30.9 ms
Jan 11, 2016 16:24:16:253 [7216] DEBUG - Pinger: Connection test to 45.33.75.206: min/avg/max: 106.5/108.6/111.2 ms
Jan 11, 2016 16:24:22:952 [7216] DEBUG - Pinger: Connection test to 139.162.7.93: min/avg/max: 334.1/337.5/343.8 ms
Jan 11, 2016 16:24:28:765 [7216] DEBUG - Pinger: Connection test to 45.79.86.131: min/avg/max: 156.3/156.3/156.3 ms
Jan 11, 2016 16:24:33:874 [7216] DEBUG - Pinger: Connection test to 82.94.168.11: min/avg/max: 15.6/21.9/31.3 ms

The list of IP addresses is obtained through this request:
https://plex.tv/services/pubsub/servers.xml

If you do not find any firewall setting that is blocking the communications to 82.94.168.11, you could try deleting the stored value and see if the server picks a different IP. - whilst server is shut down, deleting keys

HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server\PubSubServerPing
HKEY_CURRENT_USER\Software\Plex, Inc.\Plex Media Server\PubSubServer

and Restarting the server

But please first check the firewall
and please let me know which country you are in

28

@McLovin. - Could you try 0.9.15.1 please for your tests as there have been further tweaks to how the pubsub servers are connected to

29

@sa2000 - thanks for all the ideas!
I installed the version 0.9.15.1 but got the same error message again.
Also i checked my router/firewall (a simple AVM Fritzbox) but there are no specific firewall rules to prevent contacting the IP 82.94.168.11. Must say you cant really tweak the firewall in this box - but its widley popular here in Germany/Munich so i suppose this is not related to some settings in there.

Also i shutdown Plex and removed the entries from the registry but no luck - the same error message came up again.

Any further ideas?

30

Could you, as a test, simplify your network to just one local subnet and also disabling ipv6 in server network settings.

And Go through shutdown and key deletion again and restart and assuming problem remains get fresh full log file after waiting for few minutes after launch and I will flag it to the plex team to get advice. Also please get the XML for the pubsub servers.xml request mentioned in one of my earlier posts

31

I disabled IPv6 in the Plex network settings, now - as far as i know if only have one subnet running here at home (Ip Range 192.168.178.1-x) Or do you mean something different?

Also i shutdown Plex and looked for the PubSubServer/PubSubServerPing Entries in the registry but there were no entries anymore (refreshed the view, too) Even having the Server up and running for a while (10minutes+) the entries were not created again.

A refresh of the Music section was not successfull with the same error message.

Accessing the address “https://plex.tv/services/pubsub/servers.xml” with a webbrowser is working without any problems.

Please find the fresh log and the server.xml attached.

32

@McLovin. said:
I disabled IPv6 in the Plex network settings, now - as far as i know if only have one subnet running here at home (Ip Range 192.168.178.1-x) Or do you mean something different?

Three network subnets visible to Plex Media Server : 192.168.81.xxx and 192.168.178.xxx and 192.168.247.xxx

Jan 14, 2016 11:35:57:666 [2680] DEBUG - Network interfaces:
Jan 14, 2016 11:35:57:666 [2680] DEBUG -  * 1 {B3ADD3E0-9364-11E5-A038-806E6F6E6963} (127.0.0.1) (loopback: 1)
Jan 14, 2016 11:35:57:666 [2680] DEBUG -  * 4 {29FB14AF-5F65-4FEA-9F9A-CB6F7C51717D} (192.168.81.1) (loopback: 0)
Jan 14, 2016 11:35:57:666 [2680] DEBUG -  * 6 {7B25BCE4-EBCF-44F1-82D0-327DFAA78954} (192.168.178.68) (loopback: 0)
Jan 14, 2016 11:35:57:666 [2680] DEBUG -  * 7 {8559109A-74E8-4E8D-8869-B87D5104274F} (192.168.247.1) (loopback: 0)

@McLovin. said:

Also i shutdown Plex and looked for the PubSubServer/PubSubServerPing Entries in the registry but there were no entries anymore (refreshed the view, too) Even having the Server up and running for a while (10minutes+) the entries were not created again.

The symptoms are slightly different now. No successful timings got obtained for the pubsub servers

Jan 14, 2016 11:35:59:453 [8100] DEBUG - EventSource: Connecting to pubsub.plex.tv
Jan 14, 2016 11:35:59:454 [7300] DEBUG - EventSource: Resolved to 82.94.168.10
Jan 14, 2016 11:35:59:488 [3668] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 14, 2016 11:35:59:488 [3668] ERROR - EventSource: Retrying in 15 seconds.

Jan 14, 2016 11:36:14:478 [3668] DEBUG - EventSource: Connecting to pubsub.plex.tv
Jan 14, 2016 11:36:14:478 [3668] DEBUG - EventSource: Resolved to 82.94.168.10
Jan 14, 2016 11:36:14:511 [7300] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 14, 2016 11:36:14:512 [7300] ERROR - EventSource: Retrying in 30 seconds.

Jan 14, 2016 11:36:44:509 [3668] DEBUG - EventSource: Connecting to pubsub.plex.tv
Jan 14, 2016 11:36:44:510 [3668] DEBUG - EventSource: Resolved to 82.94.168.10
Jan 14, 2016 11:36:44:545 [7300] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 14, 2016 11:36:44:546 [7300] ERROR - EventSource: Retrying in 60 seconds.

Jan 14, 2016 11:37:44:540 [3668] DEBUG - EventSource: Connecting to pubsub.plex.tv
Jan 14, 2016 11:37:44:541 [3668] DEBUG - EventSource: Resolved to 82.94.168.10
Jan 14, 2016 11:37:44:579 [7300] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 14, 2016 11:37:44:579 [7300] ERROR - EventSource: Retrying in 120 seconds.

Jan 14, 2016 11:39:44:572 [3668] DEBUG - EventSource: Connecting to pubsub.plex.tv
Jan 14, 2016 11:39:44:573 [3668] DEBUG - EventSource: Resolved to 82.94.168.10
Jan 14, 2016 11:39:44:607 [7300] DEBUG - EventSource: Failure in Handshake (335544539 - short read).
Jan 14, 2016 11:39:44:607 [7300] ERROR - EventSource: Retrying in 240 seconds.

and processing list of pubsub servers for timings - did not get far failing on each

Jan 14, 2016 11:36:03:009 [9124] DEBUG - HTTP requesting GET https://plex.tv/services/pubsub/servers

Jan 14, 2016 11:36:04:147 [9124] WARN - PubSubManager: Connection to 139.162.7.93 failed: short read.
Jan 14, 2016 11:36:04:147 [9124] WARN - PubSubManager: Connection to pubsub.plex.tv failed: short read.
Jan 14, 2016 11:36:04:148 [9124] WARN - PubSubManager: Connection to 82.94.168.11 failed: short read.
Jan 14, 2016 11:36:04:148 [9124] WARN - PubSubManager: Connection to 45.79.90.28 failed: short read.
Jan 14, 2016 11:36:04:148 [9124] WARN - PubSubManager: Connection to 50.116.49.5 failed: short read.
33

I found the additional networks - have two virtual machines installed so i disabled both virtual network adapters for now. I restarted Plex but got the same error message. Also the registry keys are not created again.

Maybe my Plex installation is simply broken? Had it up and running without a fresh Plex install for quite a while now and just apply the updates every now and then. Or maybe this is related to Win10?

34

@McLovin. said:
I found the additional networks - have two virtual machines installed so i disabled both virtual network adapters for now. I restarted Plex but got the same error message. Also the registry keys are not created again.

Maybe my Plex installation is simply broken? Had it up and running without a fresh Plex install for quite a while now and just apply the updates every now and then. Or maybe this is related to Win10?

I think registry keys are not re-created because it is now not succeeding in getting any timings for the servers.
Something is terminating the communications with the pubsub servers.

I have passed the information on the plex team.

35

Ok, thanks!

36

I am thinking that whilst waiting for feedback from the Plex Team to perhaps run wireshark on the server PC and see what is happening to the communications to the IP addresses for pubsub servers

37

Just wanted to post that I just had this happen to me and had to kill the two registry entries and restart to get it working again.

Carlo

38

@cayars said:
Just wanted to post that I just had this happen to me and had to kill the two registry entries and restart to get it working again.

Carlo

Interesting - the recent changes to the code should have resulted in switching to a new IP address - ok there is still a minute or so window of time at the beginning before it switches where it would fail but after that it should detect the working and fastest connection and switch to that .

What version of plex media server ? And how soon after launch of plex media server did you have the problem ?

39

You really need to ask “me” what version? :slight_smile: Latest, greatest plex pass version which is Version 0.9.16.0

At least 3 or 4 Days to your second question since last starting Plex.

Don’t know if this is any help or not but I have Music set not to scan unless I manually add to it since it’s rather large. I tend to add music in batches to make the scan worth while. It’s been at least 2 weeks or more since I last scanned the music library.

Carlo

40

@cayars said:
Don’t know if this is any help or not but I have Music set not to scan unless I manually add to it since it’s rather large.
Wait, how? That setting was removed some time ago. Everything should get scanned now.