Plex Require secure connection support about overseerr

[Ayfteyd7Od]

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

[AwesomeAustn]

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]

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

[TomBolks]

Same issue +1

[lochstar]

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

[BananaPukeh]

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.

[sct]

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

[wuast94]

Same error, when i try to sign in with plex its works fine, then i should enter my plex hostname port etc.

my plex server is behind a reverse proxy with a valid lets encrypt cert.

but whn i try to safe i get this error:
Failed to connect to Plex: Hostname/IP does not match certificate's altnames: Host: sub.domain.tld. is not in the cert's altnames: DNS:*.{somerandomchars}.plex.direct

im on the docker develop

[samwiseg0]

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