There were 4 that started with PlexOnline* . I forget the 4th one. I backed up preference file first as well. I erased the whole line, not just the value.
The key to what I was doing was coming in from a localhost browser and not some machine on the network.
To be fair, I have a bare metal install on QNAP. Unsure if Docker installs make the difference? Also realize I’m making rudimentary suggestions, and it looks like this goes way above my pay grade.
I appreciate the suggestions! Fingers crossed they find the smoking gun soon…
Thanks. For me I can access Plex on the Nas(s) by IP. issue for me now is just via browser to plex.tv
same issue here - using Synology - was able to claim using the internal ip server link, but no access using plex.tv
Please tell us how do you fix it.
Via Browser you using your internal ip address of your NAS ?
Or Access over Internet?
I have a port forwarding on my router, so that the port 32400 is not available from Internet.
This option i had to reenter in my Plex Server Options.
Remoteaccess
I can reach my Plex servers via the internal IP address of the NAS from a computer on the same network.
https:\\ipadress-NAS:32400
Can confirm i’m up and running now. Just had to give it time for the plex servers to catch up
Finally. So, after going here: http://127.0.0.1:32400/web/index.html# I was able to log in with new credentials and see my server. I then had to uninstall ios apps and firestick app and reinstall. All is back to normal, except the web portal app.plex.tv still shows me disconnected from the server, though the workaround is fine.
All is back to fine in my plex world, except now I have to go through the laborious task of reorganizing and changing all the settings again. This was a major failure on the part of plex. If I was responsible for something this major where I work, I would lose my job, just saying.
IF YOU ARE RUNNING A CUSTOM DOCKER NETWORK, TRY THIS!
For you plex.tv works now or still same? Sorry is there a workaround on that part?
The workaround is pointing your browser to http://127.0.0.1:32400/web/index.html#. That works for me.
I believe you want to put the firefox container on HOST network and assuming Plex is on HOST network. Ideally you are going in via 127.0.0.1 or localhost. This seems to be what is tripping a lot of people up. Their plex server is configured so that some random machine on their own network cannot configure it.
Container: jlesage/firefox
Yes, I updated my instructions to include to put Firefox on the same custom docker network as Firefox
Just confirming: as @mjt_null_net just wrote, a workaround (at least for us Plex-on-NAS types) seems to be to use a browser and open Plex UI using http, not https.
I just was able to reclaim my server. However, no movie is playing, nor is any artwork displayed, so things are still funky while we wait for Plex to sort out what I guess is a certificates problem for the plex.tv service.
The good in this whole sorry episode: 1. I saw that I still have Emby installed, so I could switch over and 2. I’m using Movie Explorer Pro to watch movies, and am just about to get some streaming music service anyway, so if it’s goodbye Plex, it won’t be that hard.
How do you reclaim the Qnap plex server. The more I try the worse it gets.
The article you linked to has no equivalent steps in the current web interface. Where do you go to claim your damn server? I’ve been fighting with this for an hour and this is all because of problem on your end.
Your workstation must be on the same IP Net as your server, and they both must be on private address space
Also use the local web client, not the hosted one, and if still not prompted, try with another browser
Care to share a screen capture of what you see?
Posting here for any UNRAiD/Docker users, but I was able to reclaim my server by following these steps:
