Cannot connect to plex server

Question

Cannot connect to plex server

Opened this issue 2 years ago · 11 comments

Hi,
I've been trying out this via docker (Synology Nas) and managed to install it, but looking at the logs it just says ConnectionError: unable to connect to plex server, retrying

The only thing I added in the config is PLEX_URL and PLEX_TOKEN

Let me know if you need any other info

Answer 1 · 2022-08-23T08:06:23.000Z

Hi @joshuaLareta ! This error refers to a network connection error. By any chance, are you using localhost in your PLEX_URL ? If so, you might want to put your docker container in host mode or use host.docker.internal instead of localhost. See this thread for more information on how docker handles hostnames.

Otherwise, can you give me the PLEX_URL you are using ? Are you running Plex on the Synology NAS as well ? The dockerized version or the Synology package ?

Answer 2 · 2022-08-23T11:36:53.000Z

@RemiRigal hey, im using my local ip instead of localhost. Also, installed plex on my NAS.

PLEX_URL=10.0.042:32400

I'm able to view my plex media server just by going into the local ip

Answer 3 · 2022-08-23T12:21:34.000Z

I see two issues with your URL:

10.0.042 is not a valid IP, I assume your IP is 10.0.0.42 instead ?
You need to include the scheme in the URL, it should look like this: PLEX_URL=http://{YOUR_NAS_IP}:32400

Le me know if it fixes the issue !

Answer 4 · 2022-08-24T14:09:48.000Z

@RemiRigal sorry typo, it's http://10.0.0.42:32400

still throwing the same error. Any idea?

Answer 5 · 2022-09-02T17:19:50.000Z

Hi @RemiRigal,
I have exactly the same problem as joshuaLareta !
Plex has recently changed the authentication system since the data leak, the reset tokens too. (even after changing the token it still does not work).

Answer 6 · 2022-09-08T13:43:12.000Z

Plex has recently changed the authentication system since the data leak, the reset tokens too. (even after changing the token it still does not work).

I do not experience this issue on my end despite having changed my tokens and having the most up-to-date version of Plex.

Can any of you enable debug mode (setting the debug parameter to true in your configuration) with the latest version of PAL and share the logs. The ConnectionError: unable to connect to plex server, retrying message should be followed by a debug message with a stacktrace. Thank you !

Answer 7 · 2022-10-23T18:41:52.000Z

I encountered this error as well and enabled debug mode. The log indicated a mismatch between the SSL certificate address and the hostname. I was able to circumvent the problem by changing my Plex server to prefer (as oppose to require) secure connections and connecting PAL to the server via HTTP instead of HTTPS. Hopefully this helps others who may have been in the same boat.

Answer 8 · 2022-11-06T16:01:41.000Z

I encountered this error as well and enabled debug mode. The log indicated a mismatch between the SSL certificate address and the hostname. I was able to circumvent the problem by changing my Plex server to prefer (as oppose to require) secure connections and connecting PAL to the server via HTTP instead of HTTPS. Hopefully this helps others who may have been in the same boat.

There's no need to disable requiring TLS. Getting the right URL and Token is quite simple.
Just follow the official guide and view the XML document from one of the library items and use it's URL as PLEX_URL. It should look something like this:

https://[Local-IP].[AlphaNumeric-Identifier].plex.direct:32400/

With this address it should work. (At least it did for me, I had the same issue with http://local-ip, but with the https://plex.direct URL it's working.)

Answer 9 · 2022-11-14T15:21:02.000Z

I encountered this error as well and enabled debug mode. The log indicated a mismatch between the SSL certificate address and the hostname. I was able to circumvent the problem by changing my Plex server to prefer (as oppose to require) secure connections and connecting PAL to the server via HTTP instead of HTTPS. Hopefully this helps others who may have been in the same boat.

There's no need to disable requiring TLS. Getting the right URL and Token is quite simple. Just follow the official guide and view the XML document from one of the library items and use it's URL as PLEX_URL. It should look something like this:

https://[Local-IP].[AlphaNumeric-Identifier].plex.direct:32400/

With this address it should work. (At least it did for me, I had the same issue with http://local-ip, but with the https://plex.direct URL it's working.)

Thanks for this. It worked!

Answer 10 · 2023-01-29T18:42:43.000Z

I'm experiencing the same issue when I try this: PLEX_URL=https://127.0.0.1:32400/ or the XML url mentioned above...

Unsure what to do to proceed...

Answer 11 · 2024-08-02T23:21:05.000Z

In the same vein as RemiRigal's original response, this 'issue' may also be stemming from your Docker's default subnet, so attempting to use 127.0.0.1/localhost can lead to failure.

Instead, use your machine's internal IP for the URL.

ex. PMS and Docker are installed on the same machine, which has an internal IP of 192.168.1.123 (example, yours will be different), instead of using 127.0.0.1:32400 in the config file, try using 192.168.1.123:32400.

Just another potential avenue to troubleshoot should anyone be facing this scenario.