I have been using a reverse proxy in front of my Plex Server. I had set it up to only work over TLS 1.3. This worked for my use case, given the clients I had been using. It appears that among all the Plex apps and third-party apps in the ecosystem, only Plexamp lacks support for TLS 1.3 though. I recall reading earlier this year that there’s an update coming to the network stack for Plexamp. Is that / TLS 1.3 support coming? I’ve been enjoying Plexamp, and I’d like to standardize my personal setup on TLS 1.3. Thanks.
I don’t know why Plexamp wouldn’t support TLS, it’s more likely that it doesn’t like the reverse proxy. If you post the debug logs, there’s probably more clues in there.
Thanks for the quick reply @elan.
I’m not saying the issue in my admittedly rare case is TLS broadly, but just TLS 1.3. And the issue only arises in Plexamp.
When I changed my reverse proxy settings to enable TLS 1.2 and TLS 1.3 (instead of only TLS 1.3), the issue resolved and Plexamp works just fine.
It occurred to me to try this after looking at the logs. The Plexamp logs showed this:
DEBUG - Networking: Completed request 34: (GET https://example.com:443/) with code -35 (have 0 bytes) in 142 ms.
I couldn’t find anything on code -35, but this looked like a dropped connection or something. The reverse proxy logs had nothing. So, that suggested something about my case was creating a situation with Plexamp couldn’t connect to the server.
With other Plex and third-party apps, there are no issues with a reverse proxy setup that only allows TLS 1.3. It’s only Plexamp that seems to max out at TLS 1.2 and doesn’t yet support TLS 1.3.
Thanks.
why operating system are you seeing the error on?
possibly related:
iOS and iPadOS 14.6. The main Plex app and other apps did not have an issue with TLS 1.3.
they use a totally different networking stack.
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.
