Server Version#: 1.13.8.5395
Player Version#: Web Client 3.67.1 / Plex Android App / Windows 10 App
I am having issues connecting to my Plex server from within the LAN aswell as remotely.
This is my setup: Plex running on Windows 10 PC, testing with Laptop on same network.
When I open a browser on the server, running http://127.0.0.1:32400/web/ is running as espected, performance is good, ui responsive - streaming works fine. Using the Windows 10 app works aswell.
Opening http://[server IP] :32400/web is a different story. The connection is VERY slow, taking ~30 seconds for the login page to show. After login (which is fast since it is on http://plex.tv I guess), the loading of the main page takes another ~20 seconds. Movies can be selected, however streaming usually fails or is buffering because of slow connection speeds.
Using the plex app is similiar.
I also tried connecting with my Android, with similar results. (Both from inside the network and from the outside)
My local network performance should not be the issue. I can connect to the server well using RDP, transfering files is fast aswell. Server is reachable from outside.
I am at a loss here: I tried many things to no avail. Does anyone have any ideas?
Oh right, the server IP goes there, the forum just removed it since I used greater and lesser than signs I corrected it in the post.
I used the actual server IP during testing.
Ok, if using your local IP and accessing it remotely are slow, sounds like a network issue. Maybe a slow DNS. Can you turn on logging in Plex Web (Settings \ Web \ Debug \ Debug level (enabled). Close out all browser windows. Then reload your browser and go to the local ip address. Login if needed then just wait for the home page to load. Then go back to Settings \ Web \ Debug and select " You can view the debug logs [here]". This will bring up the text in the browser. Save the text to a file then upload that file. Then go to Settings \ Server \ Help \ Download logs. Grab that zip file and upload that too.
Can you recreate this again and get me new logs, but this time turn off verbose logging before doing so. Verbose causes too much noise when looking for a generic problem. It’s great for narrowing down specific issues, but not in this case.
I corrected it in the post.