@costinr the localappdata is different than the install location (Program Files). Can you please try to run the installer again?
@anon5074910 I believe @costinr 's issue might be different than yours. We have filed the local auth issue and are investigating. Thanks for reporting.
@Atomatth Done it 2 minutes ago, Downloaded PlexMediaServer-1.40.0.7998-c29d4c0c8-x86_64 and installed it. Same result “404 Not Found” via web browser, same behavior via app.plex.tv or via windows app client: libraries not editable.
@Atomatth No, that field was empty in my settings, I’ve never used it. I’ve filled it (192.168.100.1/24 is my local subnet) and saved the form but with exactly same results.
Do you have this path on your system? Your original logs show it as missing. Did the reinstall add it?
C:\Program Files\Plex\Plex Media Server\Resources\Plug-ins-c29d4c0c8
(Assumes you installed Plex to the C: drive in its default path.)
I removed it on my system (renamed it actually) and was able to reproduce your issue. After putting it back, the embedded web client was available again (after a PMS restart).
@pshanew No, I do not have that path, because there is that (unusual) setting I’m using: the different value set in LocalAppDataPath value in registry. My Plug-ins folder is placed in the other path, set by that value.
I’m not referring to the Plex data folder path. That’s completely separate. I’m asking about the Plex Media Server installation path that you chose during installation. It’s the path where your “Plex Media Server.exe” executable lives; the .\Resources\Plug-ins-*" folder should be in that same path.
(The registry setting you mentioned does not change the server installation path, only that of the Plex data path.)
Perfect, thanks! This confirms that the required Plug-ins folder is missing from the Resources folder in the media server’s installation path. (It should be right between ‘locale’ and ‘Profiles’ in your final screenshot.)
In fact, based on your first screenshot, it’s one directory level higher than it should be (sitting beside Resources instead of inside it). Try moving Plug-ins-c29d4c0c8 inside Resources and restart PMS. The final path to it should end up being what I posted above. Again, for reference:
C:\Program Files\Plex\Plex Media Server\Resources\Plug-ins-c29d4c0c8
@pshnew Yes, you’re perfectly right, now everything seems to be back to normal, including the capacity of editing the libraries, thank you!
Still, definitely there is a bug in the installation executable of this version, and I think that the misplacing of that folder is somehow connected to my specific configuration of that registry value.
Yep, something definitely went wrong with the installation. I wonder if uninstalling and reinstalling PMS, but leaving all the data in-place, would have corrected it? It might still be a good idea to do that (uninstall/reinstall) just to get back to a known state. If you do, just make sure you don’t use any third-party uninstallers; stick with the Windows add/remove programs feature.
I upgraded yesterday as well and didn’t have this issue, so it appears as though there was something environmental at play here.
Yes I can see that the issue was with the install - and the lack of the web-client plugin stopped the 127.0.0.1:32400 requests from working
Feb 13, 2024 22:34:26.320 [11092] ERROR - Couldn't find the file to stream: C:\Program Files\Plex\Plex Media Server\Resources\Plug-ins-c29d4c0c8\WebClient.bundle\Contents\Resources/index.html
Can you please locate the installer logs and zip and attach here
The files should have been saved in this path G:\!!PLEX\!!PLEX\Plex Media Server\Logs\Installer Logs
Find all files with names starting Plex Media Server_x64_2024_02 and copy out and zip and attach
We made changes to the installer relating to the plug-ins folder. I see it is still at the top level and not moved to the resources directory
Question: Were you updating to 1.40.0.7998-c29d4c0c8 whilst the earlier version was active and running (version 1.40.0.7775-456fbaf97) ? or did you exit / shut it down first and then update?
The log you provided is for windows machine running Plex Media Server “Storehouse” on version 1.32.2.7100-248a2daf0 on the 11th February covering period from 12:05:54 till shutdown at Feb 11, 2024 12:24:50, It appears to have been running a downgrade
I see a lot of curl errors 35 which is some certificate / tls error
CURLE_SSL_CONNECT_ERROR (35)
A problem occurred somewhere in the SSL/TLS handshake. You really want the error buffer and read the message there as it pinpoints the problem slightly more. Could be certificates (file formats, paths, permissions), passwords, and others.
Example of requests to plex.tv that failed
Feb 11, 2024 12:06:05.041 [11408] WARN - [HttpClient/HCl#2] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (35, SSL connect error) (Send failure: Connection was reset)
...
Feb 11, 2024 12:06:05.043 [11408] WARN - [HttpClient/HCl#3] HTTP error requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx (35, SSL connect error) (Send failure: Connection was reset)
Plex Media Server_x64_2024_02 and copy out and zip and attach Installer Logs.zip (159.0 KB)
Please locate files with names like this and copy out and zip Setup Log 2024-02-xx #xxx.txt Temp.zip (159.1 KB)
Question: Were you updating to 1.40.0.7998-c29d4c0c8 whilst the earlier version was active and running (version 1.40.0.7775-456fbaf97) ? or did you exit / shut it down first and then update?
I’ve installed by downloading the installer executable and launching it, without exiting/quitting the running instance.