Server Version#:1.15.3.858-fbfb913f7
Player Version#: Version 3.83.1
Windows 10.0 (Build 17763)
Hello,
I have troubleshooted this issue originally believing it was a reverse proxy issue however last night i confirmed this is reproducible locally on the server.
When visiting http://127.0.0.1:32400 and viewing PLEX in incognito mode or right after cache has been deleted from the browser everything operates perfectly. It is until you hit the refresh button in which the server list instantly shows the same server twice (Both in the top right activity section and on the top left server selection)**Both servers seen as “NEARBY”. Upon seeing the server list twice you are unable to select any libraries in the menu as it will just cause the page to blink. Attempting to navigate the settings menu from the top right button sometimes is able to load the settings however it almost always loses connection to the server after a few menu selections.
I have tried the latest main branch and beta build, both with the same results. This is a brand new windows 10 plex server as our old one finally kicked the bucket. I have tried my best to troubleshoot this issue but am unable to figure out what is causing the problem.
I would like to add, when accessing my plex server through plex.tv none of these issues are present, it only happens on localhost/127.0.0.1, custom domain url, local ip url. On any machine remotely, and on the network. It is constantly reproducible.
Do you by any chance manually add the local plex server and have DLNA scanning enabled. Normally plex Auto detection happens on the LAN. so if you manually added it it will be treated separately from the auto detect host. Will happen if you have the server running with IPv4 and IPv6 enabled or are jumping between “localhost:” and “hostname”:“port” if running locally.
Then you will have to wait for a newer server release which bundles a newer version of the web app.
Plex is not really made to be used offline.
Too many of its features depend on an internet connection.
If you really need to use it offline for a longer time, you need to take a few precautions and disable several of its features. Choice of Plex client types is also limited to those which allow the manual selection of the server IP address.
not a long time, I just don’t want to stop using plex in the event my internet connection goes down like if someone puts a trench through the data lines and there is no internet for 2 days, not everyone has redundant fibre optic connections at home
plex is a server running on a local computer, it SHOULD be able to play content without the internet (obviously features like metadata downloading won’t work but accessing existing content and playing content should work!)
I mostly run plex from the computer hosting plex, i also run plex using an app on my tv but without internet i can accept not being able to access it this way, i would be the only one using plex so multi user is not an issue, all i want to do is connect to lex on the local computer (the server) and play content
Sorry for maybe necroposting, you just said what I thought and argued here as well. But apparently this is not the approach that Plex devs went with. While you can indeed disable some multi user functions and enable lan whitelist it will still often fail without internet.
So if 100% local usage is what you’re after consider alternatives. Emby\Jellyfin (FOSS Emby fork) MAY be a bit better for LAN usage, they also have online features but I think they are more liberal for LAN use. If you’re just using it on 1 PC and some clients you can also use Kodi instead, it should allow to play locally as well as stream to other PCs on the network.
In the end VLC and Samba also works So far this is what I resort to when internet goes down. Those excruciating hours or couple days when I need to browser samba share folders manually and play everything in VLC, UGH!
So far this is what I resort to when internet goes down. Those excruciating hours or couple days when I need to browser samba share folders manually and play everything in VLC, UGH! 