Hi -
I’ve been using a VPN client and DDNS to route my traffic outside the tunnel for years. With the latest update, the remote access feature appears to be ignoring the “Custom server access URLs” function.
When I go to remote access my public IP is my VPN exit, rather than my usual router IP. I have confirmed the resolution of my DDNS to my router IP and that my custom server access URL has my DDNS public address.
Only way to make it work is bringing my VPN tunnel down so that the server sees my public IP.
Has anything changed in the latest update or on the Plex server end to cause this? No configuration changes on my end other than the server update to 1.9.0.4252.
Thanks.
1 Like
Hi !
Same problem here, Plex doesn’t recognize the custom URL option for few months and break my VPN configuration.
It would be nice if the Plex team could close this issue.
I guess this was never resolved?
If I added a second NIC, is there a way to route the Plex traffic through that? I don’t have the IP addresses or URLs to reroute, and can’t find them.
@adaigre I never resolved the issue and haven’t tested again in newer versions. I moved my VPN off my plex server…
@tornadotj there are ways to bind a process to a specific adapter or address, it depends on what OS you’re using. Search for “bind network adapter to application” for details on your specific host.
