Skip to content
RESONON

Fix Connection Problems

Find the message or the symptom, then work through the fix. Quoted blocks are what resonon or the VSCode extension prints; bracketed lines appear in the RESONON Output panel.

VSCode cannot connect

Section titled “VSCode cannot connect”

Not connected to RESONON server. Run ‘RESONON: Connect to Server’ first.

  1. Check that a server runs: start one with RESONON: Start Server, or resonon server in a terminal. A server is ready when it prints [server] Listening on 0.0.0.0:5555.
  2. Check the host and port. 5555 is the default port; a server started with --server-port listens on that one.
  3. Check that your firewall lets the connection through to the port.
  4. Start the server on the loopback address, to rule the network out: resonon server --server-host 127.0.0.1.

A server will not start

Section titled “A server will not start”

Server error: Address already in use (os error 48)

Another process holds the port — often a server you started earlier.

  1. Find it: lsof -i :5555. Stop it, or connect to it instead.
  2. Or start this one on another port: resonon server --server-port 5557. For a server the extension starts, set resonon.server.port.
  3. Binding to 0.0.0.0, the default, can need permission on a locked-down machine. Use --server-host 127.0.0.1.

Failed to start RESONON server: Could not find resonon binary. Set resonon.server.path in settings or ensure resonon is on your PATH.

  1. Run resonon --version in a terminal. If it is not found, install resonon — see Installation.
  2. If it is installed somewhere VSCode doesn’t look, set resonon.server.path to the binary.

Failed to start RESONON server: Server failed to start within 15 seconds

The server started but never reported that it was listening. Read what it printed in the RESONON Output panel, and start it with resonon server in a terminal to see the error.

The password is refused

Section titled “The password is refused”

[Auth failed for studio (10.0.0.5:5555): Invalid password]

VSCode asks for the password: enter the one the server was started with. The server takes RESONON_SERVER_PASSWORD over --password, and prints which one it uses at startup:

[server] Password protection enabled (from RESONON_SERVER_PASSWORD)

resonon.server.password applies only to a server the extension starts for you, not to one you connect to.

A terminal view shows ⚠ Authentication failed: Invalid password on its connect screen. Type the password there, or pass --password.

A server does not appear in the Servers view

Section titled “A server does not appear in the Servers view”

The view shows No servers online.

  1. Check that the server runs, and that its startup line printed.
  2. Add it by hand: choose Add Server… and enter its host and port. A server added this way stays in the list.
  3. In a terminal view, pass --host and --port to connect without the list.

The connection drops

Section titled “The connection drops”

[Lost connection to studio (10.0.0.5:5555), attempting reconnect…]

The extension tries three times to reconnect to the active server. If all three fail:

Server “studio” disconnected

  1. Check that the server still runs; restart it if it stopped.
  2. Choose Reconnect, or Pick Server to connect to another.

A terminal view does not reconnect: it returns to its connect screen with the reason, where you connect again.

A server will not play a project

Section titled “A server will not play a project”

/songs/techno needs Resonon 0.13.0; this server runs 0.12.1. Restart the server from that project to play it.

A running server keeps the version it started with, and refuses a project that needs a newer one.

  1. Restart the server from inside the project, so the launcher starts the version it pins. For a server the extension started, take the Restart server for … button on the message; restarting stops playback.
  2. If the message ends with Install with: resonon version install …, run that first.

resonon.server.path pins the extension to one binary, whatever the project pins. Clear it to let the launcher choose.

The extension and resonon disagree on the version

Section titled “The extension and resonon disagree on the version”

RESONON version mismatch: extension 0.12.1, binary 0.11.0. Update to avoid compatibility issues.

Update whichever is older: take Download Update, or update the extension in VSCode.

Nothing appears in the Output panel

Section titled “Nothing appears in the Output panel”
  1. Print it: an expression on its own prints nothing. Use print() or put().
  2. Open the panel with Cmd+Shift+U, and pick RESONON in its list.
  3. Check that the status bar shows a connected server.
  4. In a shared session, check the output filter: RESONON: Toggle Output Filter (Own / All).
Section titled “Related”