Plex-Auto-Languages icon indicating copy to clipboard operation
Plex-Auto-Languages copied to clipboard

Cannot connect to plex server

Open joshuaLareta 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

joshuaLareta avatar Aug 21 '22 15:08 joshuaLareta

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 ?

RemiRigal avatar Aug 23 '22 08:08 RemiRigal

@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

joshuaLareta avatar Aug 23 '22 11:08 joshuaLareta

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 !

RemiRigal avatar Aug 23 '22 12:08 RemiRigal

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

still throwing the same error. Any idea?

joshuaLareta avatar Aug 24 '22 14:08 joshuaLareta

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).

TERMiNAL-Network avatar Sep 02 '22 17:09 TERMiNAL-Network

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 !

RemiRigal avatar Sep 08 '22 13:09 RemiRigal

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.

saviktkr avatar Oct 23 '22 18:10 saviktkr

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.)

dom6770 avatar Nov 06 '22 16:11 dom6770

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!

saviktkr avatar Nov 14 '22 15:11 saviktkr

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...

winterborn avatar Jan 29 '23 18:01 winterborn