Database Troubleshooting

Connection Test Succeeds but the Workspace Does Not Connect

Close the existing database window and reopen the profile after updating SSH Bridge. Native database drivers are loaded by the database-window process, so an already-running window continues using the version it started with.

Connection Refused or Timed Out

• Confirm the database service is running and listening on the configured interface and port.
• Check local and server firewalls, cloud security groups, VPN routes, and allowed client IPs.
• When using Docker, confirm that the container port is published to the host.
• If the database is private, enable the SSH tunnel and test the SSH account separately.

Authentication Failed

Verify the database username, password, target database or service, and engine-specific authentication source. MongoDB commonly uses admin as its authentication source even when the application database has another name.

TLS or Certificate Errors

Use encryption settings that match the server. For SQL Server test instances with a self-signed certificate, trustServerCertificate can be enabled, but a production server should use a trusted certificate. For PostgreSQL, MySQL, Redis, and MongoDB, confirm that the server and profile agree on whether TLS is required.

Metadata Is Missing

Click Refresh in the Metadata header. The database account must be allowed to read the relevant catalog views. A connection can succeed while metadata remains incomplete when the account has restricted catalog permissions.

Backup Tool Not Found

Install the native utility named in the error and ensure it is available in the desktop application's PATH. The database server and its command-line client tools are separate installations.

Scheduled Export Did Not Run

Scheduled exports require the corresponding database window to stay open and connected on the device that created the schedule. Confirm the destination folder still exists and is writable, then use Run now to see the latest error.