I’m not really sure what caused the issue because I was at work when it started, but I can no longer access plex outside of my local network. No network topology changes were made, so I don’t think it’s a router issue. When I check canuseeme.org, it shows my ip and port as being open and accessible. I have the port manually forwarded on my router, so it’s not a Upnp issue.
Media plays fine on my local network if its accessible, but the settings menu is very slow to load, and sometimes trying to load the settings will cause the web app to lose connection to the server.
I have tried reverting to 1.16.1.1291, but the issue is still happening, so I’m really lost trying to figure it out. I have also tried disabling Windows firewall.
I need plex to be back up tomorrow for work. I’m sure I could work something out by streaming my home desktop to my work computer to listen to music, but that’s not an acceptable long term solution.
Not sure what logs I should provide to aid in troubleshooting this issue, let me know.
EDIT: I don’t know if it’s related, but in the plex console I’m seeing lots of curl errors:
Thanks, but changing DNS servers did not help. Still disconnects the server when I try to apply manual port forward settings using they ‘retry’ button under remote access settings.
Next step would be to disable AntiVira solution temporarily, and see if that makes an difference, and if not, a zip with logs in debug mode would be needed
I saw that too. The IP address associated with that error is my wireless AP, an asus RT-AC88U. It looks like plex might have thought it was a Upnp device and was trying to use it for NAT?
but again, it’s been on the network forever, so it’s not a new change.
Update now that I’m at work and can test remote access. I can view the plex player just fine, and see all my data.
Nothing will play though. Videos are all black screen with spinning circle, and music does not buffer.
Except just now it played like 30 seconds of a song out of the blue before stopping again. Scared the crap out of me because I had forgotten I had left the web page open. The remainder of the song will not buffer or load. The web player was open for ~2 hours before the song started playing.
Not sure if that’s helpful, but at least I can see the player, even if I can’t actually play anything.
I think I ahve a similar issue.
Since yesterday evening only the Windows UI I use in chrome works.
LG TV app : doesn’t work (my windows server is unaccessible and only my WDmycloud server is visible).
PS4 : same
Can’t use chromecast function either from my laptop to my TV
remote access doesn’t work either, despite checking and resetting al my router’s resstings…
The smartphone android app does the trick as I can cast from it towards my TV, but it’s really not ideal.
Probably a bug somewhere in the new update, since I upgraded two days ago.
Update 2: It started playing again out of the blue. This time the song finished, but the next one won’t play. The plex dashboard seems to think it’s playing, but it’s definitely not.
Do the Plex Media Server.log files still have log lines with 1.0.0.0 like this DEBUG - NetworkService: Browsing on interface 192.168.0.10 on broadcast address 1.0.0.0 (index: 0)
and are the https requests to plex.tv still timing out? - like in the examples i extracted
With regards to your other posts, i cannot make any comment without seeing logs covering any period where you have some issues
This was because an external request from a PlexScriptHost.exe process failed - timed out after 5 seconds
2019-07-30 06:05:00,497 (2598) : DEBUG (networking:166) - Requesting 'http://resources-cdn.plexapp.com/hashes.json'
2019-07-30 06:05:04,861 (24a8) : INFO (datakit:131) - Saved the dictionary file
2019-07-30 06:05:05,591 (2598) : CRITICAL (core:574) - Exception getting hosted resource hashes (most recent call last):
File "C:\Plex\Plex Media Server\Resources\Plug-ins-359b06978\Framework.bundle\Contents\Resources\Versions\2\Python\Framework\components\runtime.py", line 1291, in get_resource_hashes
json = self._core.networking.http_request("http://resources-cdn.plexapp.com/hashes.json", timeout=5).content
File "C:\Plex\Plex Media Server\Resources\Plug-ins-359b06978\Framework.bundle\Contents\Resources\Versions\2\Python\Framework\components\networking.py", line 265, in content
return self.__str__()
File "C:\Plex\Plex Media Server\Resources\Plug-ins-359b06978\Framework.bundle\Contents\Resources\Versions\2\Python\Framework\components\networking.py", line 243, in __str__
self.load()
File "C:\Plex\Plex Media Server\Resources\Plug-ins-359b06978\Framework.bundle\Contents\Resources\Versions\2\Python\Framework\components\networking.py", line 183, in load
self._data = self._core.data.archiving.gzip_decompress(f.read())
File "C:\Plex\Plex Media Server\python27.zip\socket.py", line 355, in read
data = self._sock.recv(rbufsize)
File "C:\Plex\Plex Media Server\python27.zip\httplib.py", line 588, in read
return self._read_chunked(amt)
File "C:\Plex\Plex Media Server\python27.zip\httplib.py", line 630, in _read_chunked
line = self.fp.readline(_MAXLINE + 1)
File "C:\Plex\Plex Media Server\python27.zip\socket.py", line 480, in readline
data = self._sock.recv(self._rbufsize)
timeout: timed out
So something blocking or affecting external url requests
[quote=“cbc02009, post:20, topic:438682”]
What I did notice that was weird was a Upnp log for a subnet that’s not on my network:
This would happen if a device on your subnet has some old IP address configuration. It would have replied ot an SSDP Search saying it is available on http://192.168.2.1:49156/gatedesc.xml
Looking at the requests to plex.tv - all the https requests are timing out like before
e.g.
Could you try one of them on a browser on the server itself
e.g. this one https://plex.tv/api/resources.xml?includeHttps=1&includeRelay=1&auth_token=xxxxxxxxxxxxxxxxxxxx
substitute the server token for the xxxxxxxxxxxxxxxxxx string.
You can find a server token as described here https://support.plex.tv/articles/204059436-finding-an-authentication-token-x-plex-token/
If it gets a response - save it to text file and send me by private message
and any delay in getting the response?
The broadcast address issue is still there. It should not have any big impact - it is just for local server discovery if not using plex.tv
Jul 30, 2019 06:04:59.199 [9064] DEBUG - NetworkService: Browsing on interface 192.168.0.10 on broadcast address 1.0.0.0 (index: 0)
Is there any special network setup ? is VMware being used? I did notice reference to vEthernet in the log
Jul 30, 2019 06:04:59.199 [1208] DEBUG - NetworkInterface: ignoring adapter 'vEthernet (Default Switch)' (fe80::c8e2:e163:daf5:7134%18,172.17.33.113) because it has no gateway
