Skip to content

Support and troubleshooting

Reporting a bug or requesting a feature

Help → Report Bug and Help → Feature Request open the same form, prefilled with the type. Fields:

FieldNotes
TitleA short description
DescriptionWhat happened, and what you expected
TypeBug or Feature request
PriorityLow, Medium, High, Critical
EmailOptional — but without it there is no way to reply
ContextGeneral, SQL Editor, Data Grid, Sidebar, Settings, Table Structure, Import / Export, ER Diagram, License, Connection
License IDOptional

On submission you get a ticket ID and a View online link for following it.

A report that gets fixed quickly names the database engine and version, the exact steps, and the error message verbatim. "Import does not work" cannot be acted on; "CSV import with a semicolon delimiter puts everything in the first column, MySQL 8.0.36, file attached" can.

Common problems

The connection fails

Use Test Connection in the connection dialog — it reports the server's own error.

  • Access denied — credentials, or the account is not allowed from your host. In MySQL an account is user and host; see User management.
  • Connection refused — nothing is listening there. Check host, port, and whether the server binds to localhost only — if it does, use an SSH tunnel.
  • Timeout — usually a firewall between you and the server.
  • Certificate errors — see SSL/TLS and SSH tunnel.

Through an SSH tunnel, the database is unreachable

Host and port are resolved from the SSH server's perspective. For a database on the same machine as the SSH server, that is 127.0.0.1 and the normal port.

Imported numbers are wrong or zero

The decimal separator in step 1 of the import wizard. European exports use a comma; setting it to . makes every number invalid. Accented characters arriving as gibberish is the same story with encoding.

The grid will not save an edit

  • No primary key — without one, a row cannot be addressed reliably.
  • A view — whether it accepts writes is the server's decision, not NabuSQL's.
  • Permissions — the account may have SELECT but not UPDATE.

A scheduled task did not run

The scheduler only runs while NabuSQL is open — see Task scheduler. If the app was open, check the task's last status, which holds the server's error message.

Knowledge Lab says the add-on is missing

The LARQL binary is not in <app-data>/plugins/larql/. See Knowledge Lab.

The license will not activate

The key is bound to a Machine ID. If the hardware changed, the key needs re-issuing — copy the Machine ID from the activation dialog and include it in your support request. See Trial and license.

Getting the details for a report

Help → About NabuSQL shows the version and build. Help → License Status shows your license state. Include both.