Check the node's Console in the panel first, and your bot's console second.
| Message | Where | Meaning and fix |
|---|---|---|
ECONNREFUSED, connection refused | Bot | The host or port is wrong, or the node is stopped. Start it and recopy the address from Overview. |
401, Unauthorized | Bot | The password does not match the one in application.yml. |
404 on connect, or a client that never gets ready | Bot | The client is for a different Lavalink version. Use a client that supports version 4. |
Track loading failed, LOAD_FAILED, Sign in to confirm | Node | The source refused. Music sites change and can block bots. Update the plugin or try another source. |
No matches | Bot | The search found nothing, or the search source is not enabled on the node. |
| The node disconnects and reconnects | Bot | The node restarted or is short of memory. Check the Usage graph and the console. |
OutOfMemoryError, node stops | Node | Not enough memory. Move to a bigger plan. |
| YAML error on start | Node | A mistake in application.yml, usually indentation. Restore your backup and edit again with spaces only. |
Slow or choppy audio
Audio quality depends on the node's CPU and your bot's connection to it. Watch CPU on Overview while playing. If it sits at its limit, a bigger plan helps. Filters and many simultaneous players use more CPU.
Still stuck
Open a ticket with the exact console lines from the node and the bot: How to open a support ticket.





