Connect NaviBeat to Navidrome.
The steps on iPhone, iPad, Mac and Apple TV, and what each error means when it does not work.
By Nenad Jokic, who makes NaviBeat.
NaviBeat needs three things from you: your server's address, a username and a password. This guide walks through the sign-in screen, then lists what each error means. It works the same for Navidrome and for other Subsonic servers.
Before you start
- Navidrome is running, and you can open its web page from a browser.
- You know its address. At home that is usually the computer's address and port 4533, for example
http://192.168.1.20:4533. Away from home it is your public address, for examplehttps://music.example.com. - You have a Navidrome user and its password.
On iPhone, iPad and Mac
- Open NaviBeat. With no server yet, it shows Connect to your Navidrome server.
- Type the address in Server URL. If you leave out
http://orhttps://, NaviBeat uses http for a home address and https for anything else. - If you have a public address and a home address for the same server, put the public one in Server URL and the home one in Local network URL (optional). NaviBeat uses the home address on your Wi-Fi and the public one when you are away.
- Type your Username and Password. When your server offers API keys, NaviBeat says This server accepts API keys. and you can tap Sign in with an API key instead.
- If a login page such as Cloudflare Access or Authelia sits in front of Navidrome, open Advanced (custom HTTP headers) and use Add header for each header it needs. More on reverse proxies.
- If your server needs a client certificate (mTLS), open Client certificate (mTLS), type the Certificate password, then tap Import certificate (.p12).
- Tap Connect. After the first sign-in, a short setup follows.
Your password is kept in the Keychain and sent only to your own server. The privacy policy says how it syncs to your other Apple devices.
On Apple TV
- Open NaviBeat. It shows Connect to your Navidrome.
- Fill in Server URL, Username and Password. Typing is faster with the Apple TV Remote on your iPhone: open Control Center, tap the Apple TV Remote, and use its keyboard.
- Behind a reverse proxy, add the headers under Advanced (custom HTTP headers). Headers set on iPhone or Mac do not carry over to the Apple TV, so type them here.
- Choose Connect.
The Apple TV form has no home address field, because an Apple TV stays at home. Certificate import is on iPhone, iPad and Mac.
Troubleshooting
When a sign-in fails, NaviBeat shows the error and, under it, the address it tried. Copy details puts both on the clipboard for a support mail, without your username or password.
"That address did not answer"
NaviBeat waited 8 seconds and nothing answered. The line under it reads Tried …, nothing answered in 8 seconds. The address may be right and just out of reach from where you are. Check these, in this order:
- Local Network permission. iPhone and iPad: Settings > NaviBeat > Local Network. Mac: System Settings > Privacy & Security > Local Network > NaviBeat. It must be on to reach a server on your home Wi-Fi. When it is off, NaviBeat says so and offers Open Settings. Apple TV has no such switch.
- iCloud Private Relay. If your server is on a private address (192.168.x.x, 10.x.x.x, .local or Tailscale), turn Private Relay off and try again.
- VPN. A VPN that routes all traffic can block addresses on your home network. Disconnect it and try again.
https or http on a home address
Navidrome on a home network usually speaks plain http on port 4533, with no certificate. If you type https:// in front of a home address and the secure connection fails, NaviBeat tries once more with http:// and keeps that. This covers 192.168.x.x, 10.x.x.x, 172.16 to 172.31, Tailscale addresses (100.64 to 100.127), and names that end in .local, .lan, .home or .internal.
A public address gets no second try, so a real certificate problem shows. If the certificate is self-signed, NaviBeat says: This device does not trust the server's certificate. A certificate from a public authority, for example Let's Encrypt, works, and so does plain http on your home network. NaviBeat has no switch to trust a self-signed certificate, because that would also accept a stranger's certificate for the same address.
A reverse proxy that answers with a sign-in page
A login page such as Cloudflare Access or Authelia answers NaviBeat with a web page meant for a browser. NaviBeat then shows Server returned an unexpected (non-JSON) response. A proxy, VPN, or iCloud Private Relay may be intercepting the connection. If the proxy refuses outright, the error reads HTTP 401 or HTTP 403.
Two ways out. Add the headers your login page accepts, in Advanced (custom HTTP headers). Or let the path NaviBeat uses, /rest/, through the proxy without the login page. NaviBeat sends the headers only to the Server URL, never to the home address.
Wrong password, or a server that refuses tokens
Wrong username or password. comes from your server. Type the password again. If it starts or ends with a space, NaviBeat warns you, because the space is sent as typed.
NaviBeat signs in with a token first. Some servers do not accept tokens, for example when the password is checked against LDAP, or when Navidrome has token sign-in turned off. When the server answers that, NaviBeat signs in with the password instead and remembers that for the server. If the server refuses that too, NaviBeat says This server refused both of the ways NaviBeat sends a password. Then sign in with an API key, if your server offers one.
Questions
What address do I type for Navidrome?
The address you use in a browser. At home that is usually http://, the computer's address and port 4533. Away from home it is your public https address.
Why can NaviBeat not find my server on Wi-Fi?
Most often Local Network access is off for NaviBeat. On iPhone and iPad it is in Settings > NaviBeat > Local Network, and on the Mac in System Settings > Privacy & Security > Local Network.
Does NaviBeat work with a self-signed certificate?
No. Use a certificate from a public authority, such as Let's Encrypt or Tailscale HTTPS, or plain http on your home network.
Away from home? Read Navidrome remote access without port forwarding. Still stuck? The help center has more, and support@navibeat.app reaches me.