-
-
Notifications
You must be signed in to change notification settings - Fork 407
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
Plex Require secure connection support #275
Comments
This comment has been minimized.
This comment has been minimized.
You can use Let's Encrypt and a reverse proxy to give Overseerr a signed certificate. |
I'm running Plex in Docker using self signed certs and a reverse proxy with Let's encrypt certs. So I don't think that's the issue here. |
The dev already said he'd add SSL support: |
A fix for this has been pushed and is being built now on the |
Failed to connect to Plex: Hostname/IP does not match certificate's altnames: IP: is not in the cert's list: Edit: Thanks to BananaPukeh's comment, I am able to connect with Secure Connections as Required when using the direct link URL, which is found from viewing an item's XML from the Get Info screen. |
Yes it works, however. When I try to connect directly to my server IP. I get an "ip not in cert" error. But it does works with the xxxx.plex.direct link |
This comment has been minimized.
This comment has been minimized.
@wuast94 This is not the place for support please use Discord. https://discord.gg/PkCWJSeCk7 |
Describe the bug
The Plex connection doesn't work when the secure connections setting in Plex is set to
Required
. I did a workaround by setting it toPreferred
.Are you on latest or develop branch?
latest
To Reproduce
Steps to reproduce the behavior:
latest
branch127.0.0.1
, don't think this is going to work since we're in docker. But anyway, I changed this to my Plex server IP172.17.0.1
and also tried my LAN IP.Preferred
Expected behavior
Overseerr should sync using secured connections.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: