"Could not reach server" error with self signed certificate

[CrazyVito11]

What went wrong

Supersonic seems to fail to connect in case the Subsonic server (Navidrome in this case) is using a self signed certificate.
This server is only accessible via LAN, which is why it's unable to use a public certificate.

The Navidrome instance is perfectly accessible via the browser over HTTPS.
Supersonic can also connect to the Navidrome instance, as long as it's using HTTP and not HTTPS.

Expected result

Supersonic allows connections to servers using self signed certificates, preferably by first having to check a box like "Allow self signed certificates" so you can optionally turn it on in case you need it, but keep the extra security check in case you don't need it.

This way you can still have an encrypted connection, even if the certificate can't be verified.

Setup information

The Navidrome instance is hosted via a Docker container and is exposed to the network via Traefik in a Docker container. The Traefik container acts as a reverse proxy, forwarding the request to the Navidrome container.

[dweymouth]

In the config file, you can set SkipSSLVerify = true. This feature hasn't (yet) been exposed in the settings GUI though

[CrazyVito11]

After updating that in the [Application] section it worked fine, thanks!

Should I keep this issue open for specifically implementing this feature in the front-end?

[dweymouth]

Should I keep this issue open for specifically implementing this feature in the front-end?

Sounds good