PMS behind Nginx Reverse Proxy - Manual Connection in iOS App

Plex Players Mobile Devices
1

So I have PMS loaded and working fine for desktop/laptop clients and such, but am having trouble with the iOS app.

I have a domain, xxxx.com, at which plex.xxxx.com points to my public IP where Nginx recognizes plex (.) xxxx (.) com and forwards it to 127.0.0.1:32400 which has Plex running in a Docker container.

The only open ports on my router are 80 and 443. In Plex, I have remote connection disabled and the only connections allowed are through localhost, or the public-facing URL.

The Add Connection field in the Plex iOS app only allows for an IP address and port, which obviously does not work for my situation. Anyone have a similar setup and knows a way to get past this limitation?

2

I second that as well. I am having a similar issue where my Plex resides behind a reverse proxy and I cannot connect remotely from my iOS device.

It works for android, for web app, or for every other platform.

It is not an issue with my firewall since there are no records of my device ever trying to attempt to connect.

My iOS client will just time out when trying to establish a connection with my Plex server behind the proxy.

Side note: I don’t understand why plex does not allow us to specify a FQDN as a manual connection and will only take IPs.

3

True. it’s not possible. Though, PMS will publish your custom server access URLs (CSA URLs) to the pubsub service, which is used by client application to get the list of available servers for their user. Side note: the remote access reachability indicator will give a false negative, it seems it first resolves the CSA URLs and then uses the ip to verify the connection (at least this was the case till last year; I don’t use a reverse proxy since).

4

What makes you think so?
It is made to support FQDNs. But you need to supply a fitting certificate for it, or it won’t work correctly.
https://support.plex.tv/articles/200430283-network/

5

Let me clarify, I meant that the iOS app is not connecting to the server and there is no option in the iOS app to manually specify FQDN of the server. So that I can point the app in the right direction.

6

The FDQN is a great feature and imo a good step in the right direction. Unfortunately, even after specifying FQDN in the custom access URL, I still could not connect via iOS.

Works with Web app, Android app, Just not iOS and yes I have tried with multiple different iphones, ipads and different cellular networks.

7

Just to be sure: you added an actual URL as https://FQDN {assumed your port is 443}, and not just the FQDN, right?

8

Correct. I double, triple checked it.

9

It’s not the first time that I read that ios devices have problems to access services behind a tls terminating reverse proxy, Oddly the same people claim that a direct tls termination in the application works for them. Honestly, it doesn’t make any sense to me. I can only assume that the reverse proxy configuration lacks some configuration items?

10

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.