FIRSTLY!
For 11 bucks a month, get your s£^$ together Plex devs!!! Jeeeezz….
I get the dreaded 401 Unauthorised, after ONE SINGLE REBOOT. Nuff said.
If you can’t help with said info, then just F$%king jog on.
If you can, give it go.
Server Version#: Latest!!!
Player Version#: All!!!
Can you post a copy of your server logs?
I am running 4 different Plex servers all on windows and dont have any of these issues. Are you trying to run plex as a service? have you ever opened Plex as an admin? (BAD IDEA)
I really admire your patience and good will, @dbirch
@Yaracuy been dealing with end user support for different things for over 20 years now. In most cases what you are seeing is the frustration venting over an issue that the user has been attempting to deal with by themselves unsuccessfully. Once the steam is released often times things become much more civilized.
If you’ll provide some info, we can help.
If you want to do this on your own, I can offer this.
It runs on the native host (Linux) or inside the container environment to talk to Plex.tv (needs a working DNS and Gateway) and get credentials setup.
Once the script and Plex.tv communicate (regardless the LAN IP addressing – which is often a problem), you’ll be able to access it provided the PMS server is on a RFC-1918 LAN or hosted in a data center
Windows, as I have indicated above.
I’ll get one of the Windows guys to come help.
Sorry I missed your tag
Virgin install. 24 hours old. Nothing done. OOTB. One single reboot F$&%s it up. For $11 per month and a defective product, you would be uncivilised as well, especially as I have been using Plex for well over a decade, on and off.
Logs.zip (699.1 KB)
Sure thing.
While I don’t know all the Windows particulars, I see things which bother me.
Therefore, to me (based on what I see in Linux), something went sideways with the installation.
Have you considered backing down to the Public (production) build 1.42.2 which is known stable ??
On Linux, when this happens, backing down from Beta and installing Public will remedy problems.
Agree with @ChuckPa to back down to the public release.
Uninstall Plex Media Server via standard Windows uninstall. This will remove the Plex application, but not the Plex Data Folder. Do not use Revo, CCleaner, or similar tools.
Reboot the PC.
Download and install the current public release, v.1.42.2.10156.
See if you can login, access libraries, etc.
If you still have problems, update the thread and include a new set of server log files.
Was running production release. Thought I would try Beta. Exactly the same issue. Works until reboot count > 0. I will go back to prod. And no Windows cleaning tools. I will leave %localappdata%, and registry entries. I’m in I.T. (on the tools), so you can be as technical as needed.
Ok. So:
Uninstalled Beta. NO cleanup performed as suggested by @FordGuy61 . Installed prod release. REBOOT count = 0. Plex is seemingly FULLY FUNCTIONAL. Server logs:
REBOOT count = 1. Plex is non functional. Server logs:
Plex Media Server Logs_2026-01-03_13-16.zip (889.0 KB)
@ChuckPa Thank you for your help. Any Windows team members want to weigh in?
