@johan.nattochdag said:
It would therefore be very good if I was able to manually specify my fixed public IP address in Plex to use for remote access. No I am forced to use the relay solution, which is a great feature, but limits the quality.
Thanks, but I would call that a work-around and not a solution.
Anyway, I cannot get it to work. Instructions might be unclear or missing.
I have tried this.
Disabled secure connections in both server and Android client.
Then tried two variants:
a) Added my public IP address to ‘Custom Server Access URLs’ in the form http://###.###.###.###. Perhaps entering IP address is not supported? See Variant b.
b) Used a domain I own for forwarding and added this to ‘Custom Server Access URLs’ in the form http://my.url.
The result is the same:
i) the client reports that the server cannot be connected to.
i) the server repports that it is not accessible remotely.
Since there are many having this problem, of which some switches VPN provider, I think this should be given better support.
@“johan.nattochdag” said:
Thanks, but I would call that a work-around and not a solution.
If you don’t supply a matching cryptographic certificate for your custom URL, encryption can not work.
And Plex Inc won’t give you a proper signed cert for your custom URL for obvious reasons.
You can supply your own certificates, the mechanism is there.
a) Added my public IP address to ‘Custom Server Access URLs’ in the form http://###.###.###.###. > > b) Used a domain I own for forwarding and added this to ‘Custom Server Access URLs’ in the form http://my.url.
@“johan.nattochdag” said:
Thanks, but I would call that a work-around and not a solution.
If you don’t supply a matching cryptographic certificate for your custom URL, encryption can not work.
And Plex Inc won’t give you a proper signed cert for your custom URL for obvious reasons.
You can supply your own certificates, the mechanism is there.
I see. The thing is this: if I would be able to force Plex to use a specific static IP address instead of fetching it dynamically from the environment I would not need to have my own domain with my own cryptographic certificate. I do understand that it would be needed if other domains shall be used, but all this manual extra work just because you do not allow to specify the IP adress to connect to, is to me a work-around. It basically means that Plex does not support VPN without port forwarding. I, and 50+ others think it could with not too much effort.
a) Added my public IP address to ‘Custom Server Access URLs’ in the form http://###.###.###.###. > > b) Used a domain I own for forwarding and added this to ‘Custom Server Access URLs’ in the form http://my.url.
Ah, that was not so clear to me since I followed the tip: “Tip!: If you don’t specify a port, the port from your Remote Access page will automatically be used.”. Since 32400 is the default on that page (surely the external port for the non-working external ip address is not the one used!?). The tip seems to be valid only if you set it explicitly, is that right?
Nevertheless, it still does not work. The server remains unavailable even if after specifying the port.
