Welcome to our forums! Please take a few moments to read through our Community Guidelines (also conveniently linked in the header at the top of each page). There, you'll find guidelines on conduct, tips on getting the help you may be searching for, and more!

Cannot Update Music Library (This server cannot reach the Internet. Please verify connectivity ...)

ferchizzleferchizzle Members, Plex Pass Posts: 26 Plex Pass
edited July 16 in Linux

Hello! I just added a some new music to one of the folders linked to the music library on my Plex Media Server on Ubuntu 16.10 and I get the following error message: "This server cannot reach the Internet. Please verify connectivity and try again." I read through the forum posts to see what other people have done to address this and have tried re-logging in with no success. I also have the log files handy but, do not know which ones to post up. Can someone please advise what my next steps should be to get resolve this issue? Thank you!

Answers

  • bbubulkabbubulka Members, Plex Pass Posts: 93 Plex Pass

    Does any other library have this issue (I assume they would)?
    When did the issue start?
    Were there any changes made before the issues started?

    PLEX Setup:
    Server Side: Dell R410 (16 Core | 16GB RAM) / Ubuntu Desktop 16.04.01 64bit / Synology RS812 & RS814 (9TB @ RAID 5)
    Client Side: Roku 4 (x4)

    Please remember to mark the appropriate answer(s) which solved your issue.

  • ferchizzleferchizzle Members, Plex Pass Posts: 26 Plex Pass

    @bbubulka thank you for your response! No other libraries have this problem - they are updating with out error. I have not attempted to add any new files to my music library since I first created it. And there have been no changes made before the issues started.

  • bbubulkabbubulka Members, Plex Pass Posts: 93 Plex Pass

    How big is the log folder zipped? Can you attach it so we can review your logs. I'm at work so I cant download my logs to give you exact names of what logs to upload...sorry :(

    PLEX Setup:
    Server Side: Dell R410 (16 Core | 16GB RAM) / Ubuntu Desktop 16.04.01 64bit / Synology RS812 & RS814 (9TB @ RAID 5)
    Client Side: Roku 4 (x4)

    Please remember to mark the appropriate answer(s) which solved your issue.

  • sa2000sa2000 Members, Plex Pass, Plex Ninja, Plex Team Member Posts: 27,565 Plex Team Member
    edited July 19

    The way Plex Media Server tests if it has an internet connection is through its dialogue with one of the servers - known internally as the Plex pubsub servers.

    A problem arose around 11am on the 16th July.

    Jul 16, 2017 10:59:03.576 [0x7f20173fe700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
    Jul 16, 2017 10:59:03.576 [0x7f20173fe700] DEBUG - MyPlex: We appear to have lost Internet connectivity, resetting device URL cache.
    Jul 16, 2017 10:59:03.576 [0x7f20173fe700] ERROR - EventSource: Retrying in 15 seconds.
    
    Jul 16, 2017 10:59:18.577 [0x7f20173fe700] DEBUG - EventSource: Connecting to 184.105.148.102
    Jul 16, 2017 10:59:18.577 [0x7f20173fe700] DEBUG - EventSource: Resolved to 184.105.148.102
    
    Jul 16, 2017 10:59:38.577 [0x7f20173fe700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
    Jul 16, 2017 10:59:38.577 [0x7f20173fe700] ERROR - EventSource: Retrying in 30 seconds.
    
    Jul 16, 2017 11:00:08.577 [0x7f2017bff700] DEBUG - EventSource: Connecting to 184.105.148.102
    Jul 16, 2017 11:00:08.577 [0x7f20173fe700] DEBUG - EventSource: Resolved to 184.105.148.102
    Jul 16, 2017 11:00:15.972 [0x7f2017bff700] DEBUG - EventSource: Connected in 336 ms.
    Jul 16, 2017 11:00:15.972 [0x7f2017bff700] DEBUG - EventSource: Wrote data, reading reply.
    Jul 16, 2017 11:00:20.682 [0x7f20173fe700] DEBUG - EventSource: Failure in ReadHeader (2 - End of file).
    
    Jul 16, 2017 11:00:25.681 [0x7f20173fe700] DEBUG - HTTP requesting GET https://plex.tv/services/pubsub/servers
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 184.105.148.102 was 96 ms.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 45.79.210.23 was 466 ms.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 139.162.216.99 was 876 ms.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 97.107.142.226 was 1454 ms.
    
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 139.162.7.93 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 139.162.144.200 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 139.162.117.249 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 23.96.218.59 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 45.79.11.43 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 184.105.148.83 failed: Connection timed out.
    Jul 16, 2017 11:00:45.709 [0x7f20173fe700] WARN - PubSubManager: Connection to 82.94.168.54 failed: Connection timed out.
    
    Jul 16, 2017 11:00:45.711 [0x7f20173fe700] DEBUG - PubSubManager: Updating best ping time for 184.105.148.102 to 96 ms.
    Jul 16, 2017 11:00:45.711 [0x7f20173fe700] DEBUG - EventSource: Failure in IdleTimeout (0 - Success).
    
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 184.105.148.102 was 594 ms.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 139.162.144.200 was 972 ms.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] DEBUG - PubSubManager: Time to connect to 184.105.148.83 was 1557 ms.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 82.94.168.55 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 45.33.77.214 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 45.79.210.23 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 45.79.11.43 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 139.162.200.94 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 103.3.62.6 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 23.96.218.59 failed: Connection timed out.
    Jul 16, 2017 11:00:55.716 [0x7f20173fe700] WARN - PubSubManager: Connection to 139.162.115.125 failed: Connection timed out.
    
    Jul 16, 2017 11:00:55.717 [0x7f20173fe700] DEBUG - PubSubManager: Updating best ping time for 184.105.148.102 to 594 ms.
    

    Also a request to plex.tv timed out

    Jul 16, 2017 11:00:25.681 [0x7f20173fe700] DEBUG - HTTP requesting GET https://plex.tv/services/pubsub/servers
    
    Jul 16, 2017 11:00:40.706 [0x7f20173fe700] ERROR - Error issuing curl_easy_perform(handle): 28
    Jul 16, 2017 11:00:40.707 [0x7f20173fe700] DEBUG - HTTP simulating 408 after curl timeout
    

    As this was a number of days ago, could you restart the server and if the problem persists please get fresh logs zip

    Actually first external connection failures were at 10:58:11

    Jul 16, 2017 10:58:11.847 [0x7f2014bff700] DEBUG - HTTP requesting GET https://plex.tv/servers/cef4ce7ebbf28fd7e3f189db13f74ebfcefad223/access_tokens.xml?auth_token=xxxxxxxxxxxxxxxxxxxx&includeProfiles=1&includeProviders=1
    
    Jul 16, 2017 10:58:27.233 [0x7f2014bff700] ERROR - Error issuing curl_easy_perform(handle): 28
    Jul 16, 2017 10:58:27.233 [0x7f2014bff700] DEBUG - HTTP simulating 408 after curl timeout
    

    Help given free on forums.            Fee-Based Personal Support & Help.        

    _______________________________________________________________________________________

    Plex Support Information              Troubleshooting               FAQs

    Plex Media Server:   Reporting Issues        Plex Web App: Debug Log    Plex Apps: Support pages and Logs    Logs: All Logs

    For list of 3rd party programs and malware / adware crashing Plex Media Server and mswsock.dll on windows, see Repeated crashing of Plex Media Server on Windows
     
Sign In or Register to comment.