Sonos: incomplete TLS handshake: no shared cipher

[jeffrey1681]

Server Version#: 1.25.3.5409 (docker)
Sonos Version#: S1 11.2.13

My issue is the same as the ones shown in these threads:

Sonos: incomplete TLS handshake: no shared cipher

Hi everyone, Thanks for having me. I am running the following configuration: Server Version#: 1.24.3.5033 (as docker) on Ubuntu 20.04.3 LTS (GNU/Linux 5.4.0-86-generic x86_64) Player Version#: Sonos Connect S1 I have the same problem as mentioned in the following closed thread: https://forums.plex.tv/t/sonos-incomplete-tls-handshake-no-shared-cipher/699668/10 Sonos this week suddenly (from one day to another) stopped playing songs from the Plex media server. The strange thing is, that I am…

Sonos: incomplete TLS handshake: no shared cipher

Server Version#: 1.22.0.4163 on Ubuntu 20.04.2 LTS (GNU/Linux 5.4.0-66-generic x86_64) Player Version#: Sonos Connect S1 Somewhere the last few weeks my Sonos is unable to play songs from Plex. I can still browse the library from Sonos apps, but when I try to play the song it doesn’t work, Plex logs shows: Mar 12, 2021 21:44:59.550 [0x7f24f3fff700] DEBUG - CERT: incomplete TLS handshake: no shared cipher Any ideas? Update Did some more digging. Plex seems to supports the following ciphers…

Starting yesterday (right after Plex updated to 1.25.3.5385) I am getting a message in the Plex log like this whenever I try to play something from Plex via Sonos:
CERT: incomplete TLS handshake from [::ffff:192.168.2.254]:41209 no shared cipher

Disabling TLS on the Plex server works, but I would prefer not to leave that off. Does anyone have any other ideas? There was a comment in an old thread about Plex changing certificates to be RSA based, but I don’t know what ever happened with that. @johnclayton Any update on that?

I updated the Plex container to 1.25.3.5409 this morning, but unfortunately that didn’t seem to help. I have an old Play:5 Gen 1 so I can’t switch to the Sonos S2 app.

[jeffrey1681]

Something else I just noticed when digging through my logs. It looks like the port requested in the error message is random and changes for each request. Is that expected? I noticed it’s not the 32400 that’s required to be open for remote access to work.

The IP address appears to be the IPv6 version of my gateway’s IP.

[johnclayton]

In your server settings, Network, make sure that Strict TLS configuration is disabled. If that doesn’t do the trick after restarting PMS we’ll probably have to wait and see if @vanstinator has any input.

[jeffrey1681]

Yes, I know that disabling TLS will make it work. I just don’t feel that “turn off the security” is an acceptable solution.

[johnclayton]

This isn’t turning off security. Hell, I don’t even allow non-secure connections for my parents’ crappy old “smart” TVs. This just allows a more permissive secure connections for clients that don’t support current standards. IIRC Sonos and some other clients were the reason this setting was added.

More info on it here.

[jeffrey1681]

Ah, I thought you were referring to changing Secure Connections to “Preferred” or “Disabled”. Disabling “Strict TLS configuration” doesn’t let Sonos work, same errors as I posted above.