Unable to add plex backend

[notthatadam]

I am able to get an X-Plex-Token, select my username, and select my Plex URL from the dropdown list. I think the problem is that my plex listens on https on port 32400, but in the dropdown to select my Plex URL, it only gives me the option to use a URL with http instead of https. When I try to finish adding the backend, I get 400: Failed to connect to backend. Empty reply from server. Is there a way I can force it to try and connect to my https port, or do I need to only use http locally?

[arabcoders]

Hi, please check this out #739 it will also be fixed in v1.0.1 which will be deployed soon

[notthatadam]

Thanks for the quick reply. I'll be watching out for it.

[notthatadam]

I installed v1.0.1, I selected my https local URL, set validate ssl certificate to no, but it still seems to be trying to validate the certificate. It's giving me "failed to Add backend. (400: Failed to connect to backend. SSL: no alternative certificate subject name matches target ipv4 address "

[arabcoders]

I have the exact same issue, and it happens no matter which of the URLs I choose. If I select one with HTTPS, I get this:

Failed to Add backend. (400: Failed to connect to backend. SSL: no alternative certificate subject name matches target ipv4 address '172.16.16.210' for "https://172.16.16.210:32400/".).

And if I select one with HTTP I get this:

Failed to Add backend. (400: Failed to connect to backend. Empty reply from server for "http://37.24.42.77:32400/".)

Can't get past this at all.

which version you are on? could you please tell me and did you enable bypass the ssl check?

[cryptochrome]

I am on the latest version 1.0.1. I disabled the SSL check, but that didn't make any difference. The only thing that worked was choosing one of the plex.direct URLs, which the UI suggests we shouldn't use.

P.S. - My Plex also runs in a docker container on the same host, and it is using host-network. Whereas WatchState is connected to the default docker bridge. Could that be the issue?

[arabcoders]

I am on the latest version 1.0.1. I disabled the SSL check, but that didn't make any difference. The only thing that worked was choosing one of the plex.direct URLs, which the UI suggests we shouldn't use.

P.S. - My Plex also runs in a docker container on the same host, and it is using host-network. Whereas WatchState is connected to the default docker bridge. Could that be the issue?

It's unlikely. Could you please try the following.

• switch your tag to :dev.
• always select disable SSL before actually making the connection as we cache the results to not get banned from plex api.

I'll also re-check the code i may have missed something. If possible check the log, there should be debug trace i am going to need to further see if i can trace source of the problem.

[cryptochrome]

Will do and report back. Thank you!

(P.S. - The caching thing you mentioned might just be the culprit, because I had SSL enabled the first time I tried to add the backend. I deleted it and re-created it from scratch, though, and still have the issue with SSL disabled).

Going to try the dev train when I am back later tonight.

[cryptochrome]

Pulled the dev image. HTTPS URL is working now (with SSL disabled). 👍