Help / Troubleshooting

My phone cannot reach the library

You added your PC to an OpenSubsonic app, pressed connect, and got a timeout, a certificate complaint or a flat refusal. Nearly every case is one of five things, none of them your licence.

The short answer

Remote access is off until you switch it on, and it starts on the next launch. Tick Enable remote access in Settings, Advanced tab, then close Vesari Stylus and open it again.
Get the address exactly right: https://, your PC's address on your home network, then :4242, as in https://192.168.1.20:4242.
Keep both devices on the same Wi-Fi, not a guest network.
Allow the certificate. The server presents a self-signed one, and clients will ask about it.
Username admin, password copied from Settings. Not your licence email, not the API bearer token.

It is not your licence, and there is no device limit

Streaming is free and the number of devices you connect is not capped. No tier check sits on the streaming path: a request is judged on whether the password matches. A refused client is not a licence problem.

Remote access, and the restart people miss

The server your phone talks to lives inside Vesari Stylus, and it is off by default. Nothing listens on your network until you turn it on. The tick box is Enable remote access, in Settings, Advanced tab, Remote Access group.

Ticking it saves the setting but does not start the server, and the app says so in a warning under the box. Close the app and open it again, and the server starts with it. A good share of "it will not connect" is exactly this.

The server also runs only while the app runs. If the PC sleeps or you close the app, your phone is cut off until Vesari Stylus is open again.

The address and the port

The server listens on port 4242 over HTTPS. Two common slips: leaving the port off, and typing http:// for https://.

To test the server without your phone, open https://127.0.0.1:4242/api/health in a browser on the PC itself. It needs no password and answers with a one-line JSON status, after a certificate warning. If nothing answers at all, the server is not running: recheck the tick box and the restart.

Same network

Your phone reaches the PC by its address on your home network, so put the phone on Wi-Fi rather than mobile data, and on the same Wi-Fi. Guest networks stop devices seeing each other, which looks exactly like the app being broken, and some routers do the same on the main network. Your PC's address can also change when it reconnects to the router, so recheck it if a setup that used to work has stopped.

Listening from outside the house needs a private link between phone and PC, a separate setup: see Listening away from home.

The certificate warning

The server speaks HTTPS with a certificate it makes for itself on first run. No public authority stands behind it, so browsers show a warning page and phone apps offer a "trust" or "accept self-signed certificate" option. On a home connection that is expected, and accepting it is how you get in.

The certificate covers localhost, 127.0.0.1, and the local address your PC had when it was made. If that address has changed since, stricter clients may refuse outright rather than offer to trust it. For a fresh one: close Vesari Stylus, open your data folder (%APPDATA%\com.garyd.audiophile-player), delete tls_cert.pem and tls_key.pem, then start the app again. It builds a new pair covering whatever address the PC has then. See Where Vesari Stylus keeps your files and settings.

If the certificate cannot be set up at all, the remote API does not start and the log says why. It does not fall back to an unencrypted connection.

Username and password

The username is admin. The password is generated for you and sits in Settings, Advanced tab, under OpenSubsonic Password, with a Copy button beside it. Copy it rather than retyping: it is 20 random letters and digits, and case sensitive.

Regenerate issues a new password immediately, but the running server keeps accepting the old one until you restart. Restart, then update every connected phone app.
The API Bearer Token beside it is a different credential, for the remote-control API. It will not work in a Subsonic app.

A client saying "Wrong username or password" is reporting exactly that: check the password first.

Firewall

Windows Firewall can block the connection before it reaches the app. If the PC answers itself on 127.0.0.1 while the phone times out, that is the shape of it: see Remote access, security and your firewall.

Read the log

Settings, Logs tab, then type subsonic in the Search box. Two lines settle whether the server is up: one saying remote access is off and no server was started, or HTTPS API listening on :4242 when it is. After that you get a line per request from your phone, with the username and password masked out.

Do not read too much into those request lines. A wrong Subsonic password comes back inside an otherwise normal reply, so it logs like any other request, without the address it came from. Your phone app's own message is the better signal.

Still stuck

Note the address, what the phone app said, and what the log shows around then, and send it with the in-app form at Settings, Support tab, Report a Bug. See Is this a bug? How to report it and what to expect after you send one.

← All help articles