Test a connection before saving

Test connection runs the same check DevOpsPad uses for real work, with the values currently in the dialog. On success it shows Connection verified in N ms; on failure it shows the error returned by the SSH server, the driver or the API server. It does not save anything.

The test opens the SSH tunnel first if one is configured, then performs a single read on the target. The whole test is limited to 15 seconds.

What is checked

Engine Check
MySQL Connect, authenticate and ping the server
ClickHouse Run SELECT 1 over the HTTP or HTTPS interface
MongoDB Connect, authenticate against the authentication database and ping
Redis PING on the selected database number
Kafka Request cluster metadata from the bootstrap broker
Kubernetes / K3s List one Pod in the chosen namespace using the chosen context

For Kubernetes and K3s, the account therefore needs permission to list Pods in that namespace (or across all namespaces when the namespace is *). See RBAC permissions.

Steps

  1. Fill in the connection dialog. When editing a connection, a blank password field reuses the password already stored in the keychain.
  2. Click Test connection.
  3. Read the result below the form:
    • Connection verified in N ms: the target answered. The time includes the SSH handshake when a tunnel is used.
    • A red error box: the message says which layer failed.
  4. Click Save connection when the test passes. You can also save without testing.

Reading errors

Message starts with Layer Typical fix
Enter a hostname or IP address without a URL scheme Form Remove https://, paths or user@ from Host
Cannot reach SSH host SSH network Check SSH host, SSH port and VPN
SSH host key verification failed SSH trust See verify host keys
SSH connection failed SSH authentication Check the user, key, password or agent
SSH forwarding to … failed Tunnel to target The SSH server cannot reach the database host and port
Driver or TLS error Target Credentials, database name, TLS certificate name
Kubeconfig context was not found Kubeconfig Choose an existing context; see kubeconfig contexts

More detail for tunnels is in SSH troubleshooting.

After saving

A saved connection has no background health check. The query header shows the outcome of the last real request: Last response at a time, Last request failed, or Not yet verified. To check again, run a query or click Refresh resources in the Explorer.

Frequently asked questions

Does Test connection save my changes?

No. It checks the values currently in the dialog and saves nothing. Click Save connection to store them.

Why is Test connection greyed out?

You are in the browser preview. Testing and saving connections only work in the DevOpsPad desktop app.