Troubleshooting

client IP is not whitelisted

Add an active allowlist entry for the public IP of the machine or network that opens the connection, then reconnect. If you use a cloud host or VPN, use that outbound public IP.

Allowlist changed but the app still connects briefly

Your app may still be using an existing open connection. Restart the app or recycle its database pool so it opens a fresh connection under the new allowlist rules.

too many connections for role

Your database user has a concurrent connection limit. Every open session from your app pool, GUI, or IDE counts toward it.

• Close unused GUI or IDE sessions.
• Lower the app connection pool size so it stays under the limit.
• Check Connections on the database detail page (sampled with storage, not realtime).
• Wait for idle sessions to time out, then retry.

Suspended for storage

If status is Suspended after storage overage, free space or move to a plan with a higher storage limit. The database can return to Active after the next successful metrics check under the limit.

authentication rejected in a GUI or IDE

Some clients try a default system database such as postgres when they first connect. Use your QubicDB database name only, and turn off options that browse every database on the server.

No tables under public (PostgreSQL)

Open the tenant schema in your client and refresh. Many frameworks create tables there by default.

Password not available

Expected after you leave the create page. Use Reset password, then store the new value securely.

Still provisioning / cannot connect yet

Wait until status is Active. Then add your allowlist IPs and connect with TLS required.

Connection still fails after TLS looks correct

• Confirm the allowlist entry is Active and matches your outbound public IP.
• Confirm username and database name from the dashboard.
• Confirm the database was not deleted or archived.
• Update stored passwords if you recently reset them.
• Check /status if many users report the same outage.