BUG: Custom Server Access URL's are only published as local

General Discussions
1

Hi

I have been pulling my hair out to get PMS to run properly behind a Reverse HTTPS proxy since 1.1 came out because it stopped working then. It used to work fine on the 1.0.x release. Web access still works fine but PLEX Clients stopped working from 1.1

I think I just discovered why. I use the CUSTOM SERVER ACCESS URLS in NETWORKS to publish my server with the FQDN and port of my reverse proxy certificate and port. However - when checking the published URL’s in your API web service the CUSTOM URL is only listed as internal - not external.
So Im guessing all remote clients ignore the published custom url and try the IP address based one thats listed as remote. But my reverse proxy neither has my remote IP as a FQDN in it’s certificate, nor does it allow access without a properly formatted URL containing the Fully qualified certificate name.

Any chance to have the CUSTOM SERVER ACCESS URLS published as remote as well?

2

I’m seeing the same thing. Did you find a solution?

3

Unfortunately not. The usecase is probably to “narrow” to be interesting for PLEX to support. There’s no responses to this problem anywhere (plex pass forums included)