SOCK5 Request

[d00dl3s]

I wanted to request the possibility of having the option to add a SOCKS5 Auth proxy. This way we can have our own “relay” without bandwidth limitations if we want to not have users connect directly to the servers real IP.

Right now Plex Server has the option for “relay” under Settings > Network > Enable Relay (The Relay allows connections to the server through a proxy relay when the server is not accessible otherwise. Note: this proxy relay is bandwidth limited)

So the option was thought of, but it would be great to give users the opportunity to use their own service / provider.

[OttoKerner]

You can already define a “custom access URL” for your server.

Network | Plex Support

[d00dl3s]

Thanks for the reply. I should clarify. I use a VPN service provider (Privado) who also provides SOCK5 auth proxy as well. So I use SOCKS5 on Deluge, Radarr, Sonarr, Jackett, etc… (also on the same server) but I would also like to do the same on Plex Media Server.

Right now I am running a reverse proxy with a FQDN on the server that also runs PMS, Deluge, Radarr, Sonarr, Jackett, but that is only being used to re-direct a HTTPS server URL I setup. For PMS, the reverse proxy forwards HTTPS from the base URL to 32400 for remote managment. (not used for PMS client connections for media) i.e managment connections

But I still leave 32400 open so remote users can connect directly (they use the server IP directly and not the domain). i.e data connection

I would also like to have the option to setup my own relay connection using a SOCKS5 server instead of the built in Plex Media server one. i.e no need to do SSH tunneling (Privado doesn’t offer that as a service). i.e data connection)

Hopefully this makes more sense.

On a side note, this is how Sonarr does it:

This is how Deluge Does it:

[PlexTv]

Apply socks5 proxy for the communication between PMS and upstream APIs (i.e. Discover, Metadata Agents APIs and crash log collection).
This is useful for PMS deployed in a censored network.