The offer of teamviewer is helpful to the devs if they come bye and ask.
I can’t spot the actual issue. Nothing is obvious to a casual user like me.
The Windows 2012 sounds old. What is the possibility that it’s so old it
doesn’t support modern TLS v3 encryption, therefore fails the TLS handshake?
What if your DNS responded too slowly just at the cruical time, and you got
a libcurl 28 timeout error?
There are a couple of empty lines in your pms.log.
Did you redact some stuff? Did you add this CERT?
certificate
Sep 24, 2019 00:01:53.073 [2248] DEBUG - CERT: Installed certificate with fingerprint 6e:37:fb:2c:5a:1a:86:e6:45:51:4d:ae:ed:ad:64:10:ff:ac:14:fa.
Sep 24, 2019 00:01:53.073 [2248] DEBUG - CERT: Installed new private key.
Sep 24, 2019 00:01:53.073 [2248] DEBUG - CERT: Subject name is /C=US/ST=California/L=Los Gatos/O=Plex, Inc./CN=*.bedc307616fc4dce803a8dfa6ee58923.plex.direct
Sep 24, 2019 00:01:53.104 [2248] DEBUG - CERT: OCSP requests for stapling will be made to 'http://ocspx.digicert.com/'.
Later the network comes up after Plex Relay finishes and we see the resource hashes 404. I don’t know if this is abnormal.
resourceHashes
Sep 24, 2019 00:02:28.165 [4804] DEBUG - Request: [127.0.0.1:49328 (Loopback)] GET /:/plugins/com.plexapp.system/resourceHashes (13 live) GZIP Signed-in Token (Smiske)
Sep 24, 2019 00:02:28.165 [4804] DEBUG - [com.plexapp.system] Sending command over HTTP (GET): /:/plugins/com.plexapp.system/resourceHashes
Sep 24, 2019 00:02:28.166 [4804] DEBUG - HTTP requesting GET http://127.0.0.1:49192/:/plugins/com.plexapp.system/resourceHashes
Sep 24, 2019 00:02:28.183 [4804] DEBUG - HTTP 404 response from GET http://127.0.0.1:49192/:/plugins/com.plexapp.system/resourceHashes
Sep 24, 2019 00:02:28.183 [4104] DEBUG - Completed: [127.0.0.1:49328] 404 GET /:/plugins/com.plexapp.system/resourceHashes (13 live) GZIP 18ms 261 bytes
Sep 24, 2019 00:02:31.473 [4808] DEBUG - Request: [127.0.0.1:49363 (Loopback)] GET /:/plugins/com.plexapp.system/resourceHashes (14 live) GZIP Signed-in Token (Sm
Then it seems to find a lot of servers
connection tester
Sep 24, 2019 00:02:28.510 [5456] DEBUG - Connection Tester: Testing the server MedieServer with 2 URLs.
Sep 24, 2019 00:02:28.511 [5460] DEBUG - Connection Tester: Testing the server Abekat with 2 URLs.
Sep 24, 2019 00:02:28.583 [5456] DEBUG - Connection Tester: Successfully tested media server MedieServer to be at https://81-161-182-141.c4c4201864a54aab8fe9c3de4fd9821c.plex.direct:32400 in 72 ms.
Sep 24, 2019 00:02:28.605 [5460] DEBUG - Connection Tester: Successfully tested media server Abekat to be at https://2-104-67-73.193d5e3b704d4ccb8c59aa748247dadc.plex.direct:23621 in 93 ms.
Sep 24, 2019 00:02:28.684 [5456] DEBUG - Connection Tester: The server MedieServer is a valid media provider.
Sep 24, 2019 00:02:28.708 [5460] DEBUG - Connection Tester: The server Abekat is a valid media provider.
Sep 24, 2019 00:02:29.713 [5456] DEBUG - Connection Tester: Testing the server Macho MedieCenter with 0 URLs.
Sep 24, 2019 00:02:33.522 [5460] DEBUG - Connection Tester: Testing the server Plex with 2 URLs.
Sep 24, 2019 00:02:33.601 [5460] DEBUG - Connection Tester: Successfully tested media server Plex to be at https://193-106-166-34.b277d791f60540f8b3f45a3ce741d251.plex.direct:32400 in 78 ms.
Sep 24, 2019 00:02:33.707 [5460] DEBUG - Connection Tester: The server Plex is a valid media provider.
Sep 24, 2019 00:02:38.537 [5460] DEBUG - Connection Tester: Testing the server plex with 2 URLs.
Sep 24, 2019 00:02:38.626 [5460] DEBUG - Connection Tester: Successfully tested media server plex to be at https://87-58-241-161.3791fd757a3d495ebcef0a9faf6e1e99.plex.direct:25397 in 88 ms.
Sep 24, 2019 00:02:38.729 [5460] DEBUG - Connection Tester: The server plex is a valid media provider.
Sep 24, 2019 00:02:39.747 [5456] WARN - Connection Tester: Error testing media server Macho MedieCenter in 10034 ms.
Sep 24, 2019 00:02:18.217 [4104] DEBUG - EventSource: Resolved 172.104.132.7 to 172.104.132.7
Sep 24, 2019 00:02:28.626 [4104] DEBUG - EventSource: Resolved 81-161-182-141.c4c4201864a54aab8fe9c3de4fd9821c.plex.direct to 81.161.182.141
Sep 24, 2019 00:02:28.643 [4108] DEBUG - EventSource: Resolved 2-104-67-73.193d5e3b704d4ccb8c59aa748247dadc.plex.direct to 2.104.67.73
Sep 24, 2019 00:02:33.794 [4104] DEBUG - EventSource: Resolved 193-106-166-34.b277d791f60540f8b3f45a3ce741d251.plex.direct to 193.106.166.34
Sep 24, 2019 00:02:38.663 [4108] DEBUG - EventSource: Resolved 87-58-241-161.3791fd757a3d495ebcef0a9faf6e1e99.plex.direct to 87.58.241.161
Some more SSL/TLS handshake errors about TMDB service (libcurl error 35)
Maybe it had an error because it found no matches. I don’t know.
TMDB service query
Sep 24, 2019 00:02:29.348 [4800] DEBUG - Request: [127.0.0.1:49352 (Loopback)] GET /library/metadata/32027/tree (14 live) GZIP Signed-in Token (Smiske)
Sep 24, 2019 00:02:29.494 [4804] DEBUG - Request: [127.0.0.1:49353 (Loopback)] GET /services/tmdb?uri=%2Fsearch%2Fmovie%3Fquery%3DToy%2BStory%2B4%26year%3D%26language%3Den%26include_adult%3Dtrue (14 live) GZIP Signed-in Token (Smiske)
Sep 24, 2019 00:02:29.550 [4804] ERROR - Error issuing curl_easy_perform(handle): 35
Sep 24, 2019 00:02:29.605 [4804] ERROR - Error issuing curl_easy_perform(handle): 35
Sep 24, 2019 00:02:29.615 [4808] DEBUG - HTTP 200 response from GET http://127.0.0.1:32400/system/agents/search?mediaType=1&id=32027&identifier=com.plexapp.agents.themoviedb&duration=5940483&filename=X%253A%255C-%253DPlex%253D-%255CFilm%2520-%2520Nye%255CToy%2520Story%25204%255CToy%252EStory%252E4%252E2019%252ECustom%252EDKSubs%252E1080p%252EHDRip%252Ex264-UNiTY%252Emkv&lang=en&openSubtitlesHash=76ba16d41e8c7f13&plexHash=84b9f5a38013a05dc06615a77770f444bc18cc97&name=Toy%20Story%204&source=bluray
Sep 24, 2019 00:02:29.616 [4808] WARN - No matches for search.
My suggestions.
- Paste in the exact path of your Toy Story 4 so we can check your naming
- See if you can set your primary DNS to use google at
8.8.8.8
and the secondary also to Google’s DNS at 8.8.4.4
to see if those avoid the timeouts.
- Tell us how your
Settings - Network - Secure Connections
is set to what?
- And your
Settings - General - Allow Fallback to Insecure Connections
is what?
- Put your server on a NUC rather than Win 2012
Sorry I can’t spot this easily. 