docsGetting started
Connect a server
Not covered by the in-app tour
The tour walks you through the app once you’re already in a library. Getting a server connected in the first place happens before any of that, so it isn’t in there at all — this page is where it actually lives.
Three boxes, not one address
The Connect screen asks for scheme, host, and port separately — there’s no single field where you paste a full URL like http://10.41.0.38:4533. The scheme is a toggle pill between http and https; the port box hints 4533 on http and auto on https, meaning a blank port just uses the scheme’s default.
The preset chips
Tapping a chip fills in scheme and port for you — you still type the host yourself.
| Chip | Scheme | Port |
|---|---|---|
| Navidrome | http | 4533 |
| Gonic | http | 4747 |
| Airsonic | http | 4040 |
| Subsonic | http | 4040 |
| Solomorph | http | 4533 |
| HTTPS · tunnel | https | (blank — scheme default) |
The HTTPS chip is for a real domain behind a reverse proxy or a tunnel like Cloudflare — not a fallback for when the others don’t work, a first-class way to reach a home server from outside your LAN.
A chip is a convenience, not the list of what’s supported: anything speaking Subsonic or OpenSubsonic works whether or not it has one. Which servers work, and what “works” means for each has the full list, plus what the OpenSubsonic extensions buy you and what quietly does less without them.
Letting Solomorph find it for you
“Find my music” sweeps your phone’s own subnet directly — the same address range your phone itself is on.
A server on a different subnet won't turn up in the sweep
If your server is routed and reachable but sits on a different /24 than your phone, the plain sweep will miss it — that’s a network-topology fact, not a bug. There’s a separate “different subnet” option where you give Solomorph a range to sweep instead, and the discovery screen names the exact range it checked, so a miss is something you can diagnose rather than a mystery. If the plain sweep comes up empty, that’s the next thing to try before assuming the app can’t see your server.
Finding nothing is not the same as the server being unreachable — typing the address in manually always works, sweep or no sweep.
If a hostname won’t resolve
A hostname that works fine on a desktop browser can still fail on the phone — most home networks have no LAN-wide DNS, so a name your router or a desktop happens to know isn’t necessarily one your phone can look up. If a name doesn’t connect, try the server’s IP address instead before assuming anything else is wrong.