Plexamp Login - Unknown Error

Hi all, I’ve searched and found a few similar issues to this over the years, but no solution. I’m trying to login to Plexamp with a work PC and get an “Unknown Error” banner at the top of the screen. The error occurs for both direct and web-based login. The log shows the following:

Sep 10, 2026 09:09:57.633 [0x0000c098] DEBUG - Networking: Create request 2: (POST ``https://plex.tv/api/v2/users/signin?login=XXXXX&password=``) network type 2.
Sep 10, 2026 09:09:57.699 [0x0000b1c0] DEBUG - Networking: Completed request 2: (POST ``https://plex.tv/api/v2/users/signin?login=XXXXX&password=``) with code -6 (have 0 bytes) in 60 ms.

I’m guessing that there is some type of firewall issue blocking the login. However, I am able to login and listen to music through the plex.tv web app interface. Is there any way to specify ports to use, or some other option to work around this issue?

Most likely your firm network uses deep packet inspection at their firewall. This works by decyrpting the packets between Plex clients and server / or plex.tv.
Then the packets are inspected and later re-encrypted with the firewall’s own intermediate certificate. However, this is detected by the Plex components and those packets are then discarded.
Because it can no longer be assumed that the data packets are unchanged.

That -6 is curl’s COULDNT_RESOLVE_HOST, so it never got as far as TLS. It failed in 60ms having received nothing, which is the name lookup failing rather than anything inspecting or re-signing the traffic. Specifying ports will not help for the same reason.

Your browser most likely works because it hands the hostname to your company’s proxy and lets that resolve it, while Plexamp looks plex.tv up itself. Worth confirming with nslookup plex.tv from a command prompt on that machine. We do not currently have a way to point Plexamp at a proxy, so if that is what is going on, there is no setting that will get you round it today.

Thanks elan, nslookup confirms that the hostname resolution is the issue:

*** XXXXX can't find ``plex.tv``: Non-existent domain

I’m sure it will be low priority, but any chance we could get proxy support as a requested feature?