New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PlexOnlineToken #60
Comments
Firstly i would try running the container as outlined in the README with standard docker commands (ie not using composer) and using net=host. Need to use as standard a setup as possible before we can diagnose any potential issues. |
I can confirm this bug. Ran the creation commands nearly verbatim and same result, restart results in no upgrade and no PMS is available to connect.
I can confirm that the container is otherwise working and data is being persisted to the named volume (i.e. the UPDATE |
try refreshing your browser if plex says no server found. |
I have already done this. force refreshed, cleared cache, tried another browser and other devices. definitely not a caching issue. I should remark that the issue is quite clearly that the |
i have in the last ten minutes or so, ran 5 pulls of the images from the hub into fresh config file locations with no failure to populate the preference file. |
let me spin up a new docker host and see what happens |
time for one of the world famous sparklyballs videos. |
interesting. The only thing that I can see that may affect the outcomes is that I am running this with
The web interface is not notifying me of an unclaimed media server on the network, this may be where things are breaking down... |
SOLVED! I was using internal dns to load the web ui, this is where things were breaking down. As soon as i hit the site with the docker node's IP address it was detected as a new PMS host and perform the initial setup (which I assume is where the Once the initial setup was complete I was able to use the internal dns again without any issues. postmortem: perhaps a One extra piece of info, if you specify the hostname (in the compose file or via |
FYI
I don't know the exact reason why plex blocks this and the german status code: But just putting the token into your <Preferences ....... I do not really know in which exact step this is failing and overall looks odd to me. edit: |
@patsissons My issue is not connected to DNS. I'm using IP. |
@drymek The issue I had wasn't specifically related to DNS, but rather how Plex web is detecting the PMS. The issue is that it is not able to detect a new server running if the hostname or IP it is running on is different from the hostname or IP you access it from. If you are still not using host networking or DNS there isn't a way to get that token (AFAIK). Without DNS, you'll need to at least run Plex with host networking to get the server detected, this is because without host networking the server runs on the internal IPv4 address (usually a 10.x.x.x address) which you cannot access from your browser. Even if you map ports and do any required forwarding, it won't work because you hit the server from the wrong address (the docker host's IP address). With host networking, the container binds to the docker host address and therefore listens on it as well. Once you do the initial setup, just redeploy your container without host networking (if you are concerned about that part) and re-enable your port mappings and everything should work fine. If host networking is not possible or desired at all, then you have to tell the container to use a custom hostname, and then set up your local DNS to point the hostname to the docker host. This is what I ended up doing and did not need to use host networking. |
host network works like a charm, but when I change it later to ports mapping, the server could not be discovered. For others: the compose file with host networking is:
UPDATE: PORTS MAPPING WORKS |
@drymek @patsissons |
My mistake - switching back to ports mapping works as well. |
@felixsteghofer Yes, there is:
|
For posterity, I was having the same issue because I was pointing my browser at the server's name from my /etc/hosts file, which would hit the web server, but present the same "server could not be found" error message described above. When I entered the IP address of the server into my browser, everything worked just fine. |
I want to use Radius to authentificate the users plex |
@nesrine19992 That's not supported by us, so don't think the linuxserver team is ignoring you but we can't help with this, however if some other person chimes in that's great though. |
thank you |
Is it possible that we can add this to the Readme? Ran into the same issue because I directly started changing my ports instead of starting in host mode. With a hour or so searching through the issues, I found this gem and it fixes it. This would be very handy to have documented. |
I've successfully installed and run docker image, but always getting message:
The web UI says (after login):
A server could not be found. Download and install Plex Media Server, and it will appear here. Where is my server?
and
Install your new server
Host OS:
docker-compose.yml file:
run command:
Docker output:
config/Library/Application\ Support/Plex\ Media\ Server/Preferences.xml (not sure what is secret, so I will remove them)
I have plex account but don't have paid subscription. Restarting docker doesn't change anything. I've removed VERSION env, but the result (except the message) is the same - no plex server
If you need any other information just let me know - I will do my best to help.
The text was updated successfully, but these errors were encountered: