Can't Access Library

Plex Media Server Desktops & Laptops
1

Server Version#: Unable to Check due to it being Inaccessible
Player Version#: Web Version 4.100.1

I do not have any logs currently, as I am not able to access the server. If I restart, the server will work again for a while and then do this again.

This has been going on for months for me with no updates. I have been providing verbose logs, and offering to run a custom build, check additional info, but no help.

Please someone at Plex help us out here, as I know I am not the only one. Not that you will care at all, but at this point I will stop paying Plex because they can’t even help me get a working product.

2

Use “Method 2.2” from this post: You need to reclaim your server, but don't dare to touch the Windows Registry

Tell your web browser to NOT delete the cookies from plex.tv when it is closed. Many browsers do that now by default, so you need to create an exception rule in their settings

Some tips for trouble free operation of a Plex server:

  1. Put your Plex server inside a private network/home network
  2. Avoid home network “fragmentation”
  3. Use a designated private IP range for your private network
  4. Give the server and your NAS static local IP adresses
  5. Avoid using more than one network adapter in your server machine
  6. Disable power saving for network adapters
  7. Don’t let hard drives spin down their platters
  8. Don’t rely on Windows to store access credentials to file servers/NAS devices
  9. Configure “DNS rebinding protection” in your router/DNS resolver
  10. Make sure all involved devices have accurate date/time
  11. Always use a “staging” folder for preparing your media files
  12. Don’t point a Plex library to a “naked” drive letter
  13. Stick to the Plex naming conventions
  14. Never mix up media folders, Plex data folder, and the Transcoder temporary folder
  15. Before assigning an email address to a plex.tv account, make sure it’s actually ready to receive mail
  16. Avoid using a VPN service
3

Thank you, I have followed “Method 2.2” and reclaimed my server. However, I have done this before, so I am not very hopeful about the outcome.

I follow each of your recommendations for trouble free operation of a Plex server, except the hard drives. Considering that the server gets used to watch movies 3-4 times per week, it does not make sense to rack up so much wear on the drives, so the computer goes to sleep and is woken via WOL before attempting to access from a viewing app (phone, Apple TV, Roku, Smart TV, etc)

4

Actually, there is more wear on the drives when you start and stop them all the time. The counter for startups is one of the key parameters for assessing the remaining lifespan of a hard drive.

5

Thanks @OttoKerner, yes, it does play a factor, especially with a lot of starting and stopping. But my setup is not even powering up once a day, and the breakeven point is unknown (as far as I know) as to when powering down is “better”. For example, if I am not going to use the drive for 2 years, then it’s most likely better to stop and restart in 2 years. Whereas 10 minutes would obviously make sense to stay spinning.

Anywho, hard drive longevity aside, I will now wait and see if this method of claiming my server fixes anything.

What is happening when I get the “Not Authorized” warning on a technical level? Is there a registry entry that stores that my account owns this server, and it gets corrupted? This issue seems to happen approximately a week after I restart the server, is there like a time that the authorization stays valid for before it needs to be renewed (something akin to a DHCP lease time)?

6

I can’t tell with certainty.
My working theory is that the access token to your account got either invalidated in your account (this can happen if you delete anything in here: https://app.plex.tv/desktop/#!/settings/devices/all )

or the client lost the token (this happens when the cookie from plex.tv is deleted)

or the server lost its own token (this happens when the server token is removed from the Windows registry. Do you use software which claims to “optimize” your registry? Don’t. It’s snake oil.
Another possibility would be if you let Windows perform a reset to a system snapshot, which was created before the server was claimed or installed. Reverting to an older snapshot is something that should not be done regularly. It can mess up the system considerably. Avoid it and certainly don’t perform it pre-emptively.

7

I dont know for sure but your issue looks related to mine, which was solved by fixing a DNS issue. Look at my resolution in my post “Cant Connect Securely”. Hopefully that will fix yours as well.

8

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