Troubleshooting
Fix common RowDex problems: connection refused or timed out, authentication failed, SSL and certificate errors, SSH tunnel failures, Redis and MongoDB issues, and locked features.
Most connection problems come down to a handful of causes. Find your symptom below. The Test connection button in the connection form is the fastest way to check a fix without saving anything.
Can't connect#
Connection refused or timed out
RowDex could not reach the server. Check the host and port, and that the database is running. If the server is in the cloud, add your current IP address to its allowlist or security group. If it is on a private network, connect through a VPN or an SSH tunnel.
Password authentication failed
The server rejected the username or password. Retype the password, check the username, and confirm that user is allowed to log in from your address. If you pasted a connection URL, characters such as @ : / ? # in the password must be percent-encoded. Switch to Standard mode to type it as-is.
Database does not exist
Leave the Database field empty to connect to the server, then pick a database from the sidebar. Names are case-sensitive on many servers.
It works in another client but not RowDex
Compare every field, especially SSL mode and the database name. If the other client uses an SSH tunnel or a certificate, set the same in the connection form.
SSL and certificates#
The server does not support SSL
You required encryption on a server that does not offer it. Change the SSL mode to Prefer, or switch SSL off for a local development database.
Certificate verify failed or unknown authority
You chose Verify CA or Verify full but RowDex does not trust the server's certificate. Set the CA certificate path to the provider's CA bundle. Managed databases such as AWS RDS and Azure publish theirs.
Hostname does not match the certificate
Verify full also checks the hostname. Connect using the exact hostname on the certificate, not a raw IP address or an alias.
SSH tunnels#
The tunnel fails to open
Test the SSH details on their own: host, port 22, username, and the password or key. For a key, check the path, that the key is the one the server expects, and that you entered its passphrase if it has one.
The tunnel opens but the database is unreachable
The database host and port are resolved from the SSH server's side. Use the database's private hostname or IP, such as the internal RDS endpoint, and check the SSH server is allowed to reach it.
Redis, MongoDB and BullMQ#
Redis says NOAUTH or authentication required
The server needs a password. Enter it in the password field. For a managed Redis that requires TLS, switch on SSL / TLS.
No keys appear
Check the database number. Redis has databases 0 to 15, and your data may be in a different one than the default 0.
MongoDB Atlas will not connect
In Atlas, add your IP address under Network Access. Use the mongodb+srv connection string in Connection string mode, and make sure the username and password belong to a database user, not your Atlas login.
BullMQ shows no queues
Queues only appear on a Redis connection that actually holds BullMQ data. Check you are on the right Redis, and the right database number.
In the app#
I cannot edit a cell, or delete is greyed out
Editing needs RowDex to know which table the result came from, and deleting needs a primary key to identify each row. Open the table from the sidebar rather than running a custom join, or add a primary key. Also check the connection is not read-only.
A feature is locked or says it needs Pro
MongoDB, the BullMQ monitor, unlimited connections and saved queries across connections are Pro features. If you have Pro, sign in with your purchase email so your plan syncs, then restart the app if it does not update.
Connection limit reached
Basic allows 2 active connections at a time. Disconnect one, or upgrade. See Plans and limits.
The query seems to hang
Click Stop to cancel it. Add a LIMIT, filter on an indexed column, or check the plan with EXPLAIN. On PostgreSQL, the Server activity panel shows whether the query is blocked by a lock.
I was signed out
A new sign-in on another computer can replace the oldest device when your account is at its device limit. Sign in again. See Sign in and devices.
Was this page helpful?