Skip to content

Fixing Connection Issues

To find out where a connection fails, open the connection and click Test Connection in its Connection tab. The test shows whether DbVisualizer can reach the server, connect the SSH tunnel, if there is one, and log in to the database. See Testing a connection.

The connection times out or is refused

Messages such as "Connect timed out", "Connection refused" or "Communication link failure" mean that DbVisualizer can't reach the database server. Check that Database Server and Database Port are right. If they are, the cause is usually outside DbVisualizer: the database server doesn't accept network connections, or a firewall or VPN blocks the port. Ask your database administrator or IT department.

The driver doesn't accept the connection details

If you enter a database URL yourself, a syntax error in it usually gives one of these messages:

  • "The selected Driver cannot handle the specified Database URL."
  • "Invalid number format for port number"

Use the Server Info format instead, so that DbVisualizer builds the URL for you. If you must enter a URL, replace all placeholders in angle brackets, such as <1521>, and check the syntax. The message is also shown when the connection uses the wrong driver.

The login fails

When the database rejects the login, the message usually says why. Check the user name and password, and ask your database administrator whether your account is allowed to connect from your computer. For the authentication options of a connection, see Saving Credentials.

The driver can't be downloaded

DbVisualizer downloads most drivers from Maven repositories on the internet. If the download fails, for example with "The database driver could not be downloaded":

  • If your network uses a proxy, set it in the Proxy Settings category in Tools → Tool Properties.
  • To check that DbVisualizer can reach the repositories, click Test Maven Connections in the Driver Manager category in Tools → Tool Properties.
  • If a Certificate is not trusted dialog or a "PKIX path building failed" error is shown, see "Certificate is not trusted" is shown.

If you can't reach the repositories at all, you can add the driver files yourself, or use your own repository. See Managing Database Drivers.

The SSH tunnel fails

Click Test Connection to see whether the SSH tunnel works. If you can't connect to the SSH server, try the other SSH Implementation in the SSH configuration, since they support different algorithms. See Using SSH Tunnels.

The connection drops when it is idle

If the connection is closed after it has been idle for a while, see Handling Dropped Connections.