Troubleshooting

Troubleshooting

The application is blocked on first launch

The 0.7 beta is intentionally not code-signed. On macOS, use Finder → right-click LakeDB → Open. On Windows, verify the package came from this repository before proceeding through SmartScreen. On Linux, make the AppImage executable.

A restore did not complete

Do not retry repeatedly against important data. LakeDB creates a recovery backup before configuration and SQL restores; copy the path shown by the app, preserve that file and inspect Diagnostics. For SQL restores, verify permissions, free disk space, server version and the selected target schema before retrying in a non-production environment.

A connection fails

Check the host, port, username, server network access, VPN, database permissions, TLS/CA configuration and SSH key/agent. The copyable connection diagnostic distinguishes common DNS, timeout, authentication, TLS and permission errors.

A table cannot be edited

Editing requires a primary key or a complete non-nullable UNIQUE index. It is also disabled for unsupported views, generated-column cases and read-only connections.

Results are truncated

LakeDB limits rows and retained bytes to keep the desktop app responsive. Adjust the result limit in Preferences, or add filters and limits to the query.

Imported passwords are missing

Other clients may use credential formats LakeDB cannot decrypt. Enter a password manually or apply global credentials in the import preview.

Open View → Diagnostics for startup, IPC, connection and SSH events. Reproduce the issue once, copy only relevant entries, remove sensitive details, then use the bug report form.