New Server - Unable to create

Plex Media Server
,
1

Server Version#:1.40.3.8555-fef15d30c
Player Version#:[null]
OS: Windows Server 2022 Datacenter

Issue: unable to create a new server

Steps to reproduce issue:

  1. Downloaded the media ( PlexMediaServer-1.40.3.8555-fef15d30c-x86_64.exe ) from the downloads page.
  2. Installed PMS to non-standard location and followed these instructions to create the appropriate registry key.
    image
  3. Started PMS
  4. Authenticated with my Plex account after the browser popped up to https://app.plex.tv/auth/…
  5. Then this pinwheel’d forever
    image
  6. While waiting, I noticed the “More >” tab appeared and disappeared frequently:
    image
    image
  7. Next, I opened the System Tray and launched Plex by clicking “Open Plex…”
    image
  8. Upon launching the local Plex installation from the previous bullet point, I was met with the “Not authorized” message.
    image
    image705×344 27.4 KB
  9. I performed what is stated in the support article.
    image
  10. After this, I started PMS again, logged in and the issue persists.

I have tried this multiple times on multiple machines and tried older binaries, all with the same result. What’s interesting is, my old server doesn’t appear to exist. When I click on the “More >” tab, I can see my friends’ servers listed and below that I just see “Plex” and unable to interact with this:
image

I have also tried claiming a new token using plex.tv/claim, however, this seems to relate to situations where there is a server that just needs to be reclaimed. The support articles seem to indicate there is a prompt to enter a claim token, but I’ve yet to be presented with one. My server doesn’t seem to exist and I don’t have the option to create a new one. Regardless, I tried creating a new token and used a SSH session to apply it like I’ve seen in other discussion threads and my result is always “401 Unauthorized” when using the command curl -X POST “http://my_host_name:32400/myplex/claim?token=newly_created_token” where “my_host_name” is my server IP address & the “newly_created_token” is always something “claim-*”

I also tried sifting through the logs using this support article and it doesn’t appear to be certificate related as I found where Plex identified it was missing a cert, generated a new one and installed it successfully.

Again, this is a new PMS installation on a new server. (My old server bit the dust.)
I’ve spent a number of hours investigating this so I figured someone else my have experienced it and can lend a hand.

2

There is no reason to do so, particularly if the custom location ends up being on drive C: anyway.
The default program location folders are under special protection by Windows. You should use this.

The install location has nothing to do with the location of the Plex data folder. Which means if you wanted to move the install location for backup reasons, you’d achieved nothing. Because what you need to backup is not the program folder. It’s the registry data and the Plex data folder.

So, uninstall Plex server
Remove that registry key

Now install Plex server in the default location.
Then continue with the procedure in this post: Plex install fix for Windows Server (Claim issue)

3

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.