I’m having all kinds of issues accessing my Plex server after setting up Plex to be accessed via a Custom URL.
I have Plex setup behind a reverse proxy using a Letsencrypt SSL cert and a custom URL (https://plex.mydomain.com:443). From outside my network i can connect to plex fine via the the Custom URL. I can see my dashboard fine. However, clicking any any library or Live TV/Recordings just refreshes the dashboard instead of actually loading that library section. When I try to go to Settings sometimes I can get to them, sometimes I get “No Soup For You!” (see attached screenshot).
Sometimes when I click on the Server drop down in the top left it will show two two servers there both with the same exact name.
I’m not sure where to go from here in troubleshooting this as custom URL is totally accessible from outside my network and I have a log on the firewall rule allowing inbound over 443 and I see that traffic passing matching that rule when I’m connecting.
Plex Engineering doesn’t like MITM proxies in the SSL stream. You’ve created a MITM scenario by having one. In order to satisfy the PMS endpoint, you have to pass all the credentials, in the format provided, and maintain the TLS / SSL ,
Proxies can be good but if it’s unclaimed / not your server, nothing is going to work.
BlockquotePlex Engineering doesn’t like MITM proxies in the SSL stream. You’ve created a MITM scenario by having one. In order to satisfy the PMS endpoint, you have to pass all the credentials, in the format provided, and maintain the TLS / SSL ,
Proxies can be good but if it’s unclaimed / not your server, nothing is going to work.
It is my server. I’m just running a Letsencrypt docker with nginx built into it on the same network as my plex server. How else would I be able to connect to my PMS over https using my own cert?
