Troubleshooting

“can’t reach the server — check that it’s up and on this network”

The connection itself never opened — refused, reset, or the host couldn’t be found at all. Usual causes, roughly in order of how often they turn out to be it:

• The host or port is wrong.
• The server itself is down.
• Your phone is on a different network than the server — guest Wi-Fi, mobile data, a different VLAN.
• The hostname doesn’t resolve from your phone. Most home networks have no LAN-wide DNS, so a name that works fine on a desktop can still fail here — try the server’s IP address instead.

“the server took too long to answer — trying again may help”

A timeout — the connection opened, but nothing came back in time. Often transient; the suggestion in the message is the real advice here.

“secure connection failed — the server’s certificate was refused”

This is the https gotcha almost every self-hoster hits eventually: your server is using a self-signed certificate, or one from an authority Solomorph doesn’t trust. A browser you’ve told to trust that certificate will still refuse it here — Solomorph doesn’t inherit that exception, because it isn’t a browser.

“the server answered, but not in Subsonic’s language”

Something is listening on that host and port, but it isn’t a Subsonic API. Usually means the port number is wrong, or a reverse proxy is serving a web UI at that address instead of passing through to the actual server.

Wrong username or password

Solomorph doesn’t write its own message for this one — whatever your server says back is what you see, unchanged. If that message is confusing, that’s a question for whatever you’re running, not for Solomorph.

Getting a report that’s actually useful

No music showing up after connecting your phone as a source isn’t a connection problem — see Music on this phone for what actually controls that.