Skip to content
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

Closed
BananaPukeh opened this issue Dec 14, 2020 · 9 comments
Closed

Plex Require secure connection support #275

BananaPukeh opened this issue Dec 14, 2020 · 9 comments

Comments

@BananaPukeh
Copy link

BananaPukeh commented Dec 14, 2020

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

Are you on latest or develop branch?
latest

To Reproduce
Steps to reproduce the behavior:

  1. Do a fresh install on Docker using the latest branch
  2. Notice a Plex login dialog, and sign in.
  3. Overseerr will display a server connetion page which also defaults to 127.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 IP 172.17.0.1 and also tried my LAN IP.
  4. Fill in the correct Plex port.
  5. Save the settings
  6. Notice that the application is not responding, nor loading libraries from Plex. Sometimes a "Websocket hung up" error appears.
  7. Go to Plex server settings > Network > Secure connections > Change it back to Preferred
  8. In Overseerr, try to sync again and notice it only works with unsecured connections.

Expected behavior
Overseerr should sync using secured connections.

Desktop (please complete the following information):

  • OS: Windows 10
  • Browser Chrome 87.0.4280.88
  • Version 1.3.2
@TomBolks

This comment has been minimized.

@lochstar
Copy link

You can use Let's Encrypt and a reverse proxy to give Overseerr a signed certificate.

@BananaPukeh
Copy link
Author

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.

@Ayfteyd7Od
Copy link

The dev already said he'd add SSL support:
"I will add SSL support tomorrow though."

@sct sct closed this as completed in 3ba09d0 Dec 15, 2020
@sct
Copy link
Owner

sct commented Dec 15, 2020

A fix for this has been pushed and is being built now on the develop tag. Let me know if it's solved!

@sct sct reopened this Dec 15, 2020
@sct sct closed this as completed Dec 15, 2020
@AwesomeAustn
Copy link

AwesomeAustn commented Dec 15, 2020

Failed to connect to Plex: Hostname/IP does not match certificate's altnames: IP: is not in the cert's list:
I checked the SSL box.

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.

@BananaPukeh
Copy link
Author

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

@wuast94

This comment has been minimized.

@samwiseg0
Copy link
Collaborator

@wuast94 This is not the place for support please use Discord. https://discord.gg/PkCWJSeCk7

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants