Sander

I assume the error is from: https://github.com/flyte/upnpclient/blob/develop/upnpclient/ssdp.py#L126 I'm not sure, but maybe you can overwrite that ... ? log = _getLogger("ssdp") log.error("Error '%s' for %s", exc, entry) EDIT: Commenting out...

I had that too with Chrome. Mark it as safe

> Wonder what triggers it? The list of IP addresses in the setup? For me: a hostname via a dyndns provider (duckdns.org). So collateral damage caused by other host within...

So @GOATS2K ... the domain you blacked-out ... is that a shared / dyndns domain, or your own domain ... ?

> This is my own domain. Wow. DId you click Request Review?

> I did, so I am waiting to see if that changes anything. :) It did work for my hostname via duckdns (on which I have a sab instance)... no...

Also from the same Radarr 3.0.0 (but now with different client approach): different intermediate traceback `SSLV3_ALERT_CERTIFICATE_UNKNOWN`, and then the same `ssl.SSLZeroReturnError: TLS/SSL connection has been closed (EOF) (_ssl.c:2471)` and cherrypy/cheroot...

> It sounds like your CherryPy app uses a self-signed certificate that is not added to Radarr's chain of trust. And so when Radarr doesn't confirm the received certificate as...

Cross-testing between Linux and Windows: Radarr (in docker) on Linux ... connecting to cheroot-mini-server on Windows ... **No** SSL errors! That is weird. That means Radarr-on-Linux behaves differently than Radarr-on-Windows?...

On Linux, in a env, I'm able to install cheroot 8.4.4. From Windows I connect to that Linux instance, and ... SSL errors. So 8.4.4 does not solve it. EDIT...