had the file still saved in my download folder on desktop luckily enough, its an oldish 1 but works , before i installed it i had already tried ll the various methods of a clean install and even deleted the reg entry and the folder on the user appsdata etc
Same issue on Windows 10 :
Plex Media Server v1.10.0.4523-648bc61d4 - Microsoft PC x64 - build: windows-i386 english
http://127.0.0.1:32400/web/index.html
Plex is not reachable.
Make sure your server has an internet connection and any firewalls or other programs are set to allow access.
Plex Media Server.log :
Dec 11, 2017 10:14:31.946 [7940] INFO - Plex Media Server v1.10.0.4523-648bc61d4 - Microsoft PC x64 - build: windows-i386 english - GMT 01:00
Dec 11, 2017 10:14:31.946 [7940] INFO - Windows version: 10.0 (Build 16299), language it-IT
Dec 11, 2017 10:14:31.946 [7940] INFO - 4 3193 MHz processor(s): Architecture=0, Level=6, Revision=15363 Processor Identifier=Intel64 Family 6 Model 60 Stepping 3, GenuineIntel
Dec 11, 2017 10:14:33.118 [8540] INFO - Successfully retrieved OCSP response
Dec 11, 2017 10:14:34.007 [5004] WARN - Crash: Crash reporting disabled
Dec 11, 2017 10:14:37.317 [8752] WARN - Sync: Couldn’t get sync lists without subscription.
Dec 11, 2017 10:14:39.817 [10012] INFO - LibraryUpdateManager path watching is disabled
Dec 11, 2017 10:15:41.868 [8544] ERROR - Error issuing curl_easy_perform(handle): 28
Dec 11, 2017 10:15:41.868 [8544] ERROR - HTTP 408 downloading url https://meta.plex.tv/t/theater?language=it&subtitleLanguage=it&redband=0
Dec 11, 2017 10:15:41.868 [8544] ERROR - IVA: Error downloading trailers for source 1.
rolled my server back to 1.5.6.3790 like @REDBULL39 and it seems to be working so far. I don’t really like running an old version but may have to until this issue is resolved
@gvoniatis said: @Zekinder is the issue still resolved or has the problem come back yet?
No more issue since the rollback. I’ll keep this thread updated.
After 24 hours, same issue is back, even with Plex-Media-Server-1.9.3.4290-9798172d4.
At this point, i don’t think the issue is about the new PMS version, but more about a change in secury policy about the authentification server.
We definitely should not have this problem when attempting to connect to our own private servers on LAN.
I don’t know if this is the same fix for everyone, but seems like Google DNS is having some issues. Changing my DNS to another service (used Quad9: 9.9.9.9) fixed the issue. Hopefully this is helpful to some of you.
@markusvitz said:
Have you changed the DNS on the server or on the client?because on the client there is no difference.
On the server. My server was showing up as not reachable or indirect connection (would hop back and forth), but I could connect to the server through the internet (teamviewer). I logged into my server and changed the DNS and it fixed the issue.
I also tried this but found the issue came back with any dns I used. Temporary fix only. I think its time someone actually accepted there is an issue here.
Plex server updated a couple days ago, but the issue is still present. Usually by restarting the computer etc I can get it to work again, but not this time
This can’t be serious. When we pay for SW we usually expect Service & Support when needed. This is not support, it’s a joke. Every other sentence we are told to send in our log files and then nothing happens.
Lots of people sending their PMS logs, even though it seems to be clear that the problem is on their end, but where is the so called support?
The only sentence from PLEX is: “We need your logfiles to help.”
PLEX engineers are not really contributing so we could call it support or at least they care about their paying customers.