Plexamp, at least on Mac clients, does not honor the system settings for the proxy.
Using system proxy settings should be an easy lift on at least Mac and Windows, and there shouldn’t be any need to provide customization. (Linux is always fun for system proxies, alas.) Unfortunately, you can’t even sign in via browser on a proxy-required network with Plexamp for Mac/Windows, presumably as it tries to contact Plex’s servers for a code.
It would be nice if the client automatically supported both proxy autoconfiguration files (PACs are JavaScript files to evaluate which proxy to use) and static proxy servers (such as http://outbound.company.com:8080/ including any specified authentication and exclusions).
My experience is that it’s nearly a 50/50 distribution in the wild, between the two types. However, if one must be prioritized, I’d suggest PAC files as you can write a PAC that uses static proxy servers but the reverse is not possible.
Further, in the wild, HTTP proxies seem to heavily outnumber SOCKS proxies (except for things like SSH tunneling and VPN services).
Custom proxy configuration, would likely be welcomed by some (for example, people who only put certain traffic over certain connections via an HTTP proxy). But it likely would be easier to support an initial deployment that takes system settings and get that right, before adding the ability for users to type invalid (but, to them, seemingly correct) values and blaming the app. My experience is that users will often just type the hostname, not the protocol or port, for instance.
This feature request was opened at the suggestion of @McWanke in the 2024 Fireside Chat topic. The previous topics I’ve seen have gone unaddressed and I cannot find them now to link, and they would be long since closed anyhow. Hopefully this one catches at least the community’s interest, as it is a blocker for moving off paid subscription services onto Plexamp for people on large-company work computers, for instance.
