Connection Troubleshooting

Use this guide if you are adding a new Redis connection and the test or create flow fails.

How to Add a Connection

1. Open Connections in the app.
2. Click Add Connection.
3. Fill in:
   • Connection Name
   • Connection URL
   • Environment
   • BullMQ prefix (match your worker and queue configuration; default bull)
   • Allow self-signed TLS certificates (only when your provider requires it)
4. Click Test to verify connectivity before saving.
5. Click Create Connection.

Common Connection Issues

TLS Encryption

Use rediss:// when your Redis provider requires TLS. Use redis:// only for a connection that does not require TLS.

Self-Signed TLS Certificates

Some managed Redis providers, including Heroku Key-Value Store, terminate TLS with self-signed certificates. Durabull validates TLS certificates by default, so these connections fail unless you opt in.

When adding or editing a connection:

1. Use a rediss:// URL.
2. Enable Allow self-signed TLS certificates.
3. Re-run Test before saving.

For env-driven connections, set:

DURABULL_REDIS_URL_MAIN=rediss://...
DURABULL_REDIS_URL_MAIN_ALLOW_SELF_SIGNED_CERTS=true

Only enable this when your provider requires it. It disables certificate authority validation for that connection.

IP Allowlisting

Allowlist the outbound addresses of the machine or service running the Durabull API, which opens the Redis connection. Your browser's address is not the Redis client address.

• Self-hosted: use your server or hosting provider's current outbound addresses. For Render, obtain the service's current ranges from Connect → Outbound; see Render's outbound IP guide.
• Desktop: allow the workstation's network egress address.
• Durabull Cloud: confirm the current Cloud egress ranges with Durabull support at hello@durabull.io before changing your Redis allowlist. Hosting ranges can change.

For Docker, localhost refers to the container. Use a shared-network service name such as redis, or the host-access address supported by your Docker environment.

Quick Verification Checklist

• Confirm host, port, username, and password are correct.
• Confirm TLS is enabled when your provider requires it.
• Confirm network allowlists and firewall rules permit the API server's outbound addresses.
• If the connection succeeds but no queues appear, verify the Redis database number and BullMQ prefix.
• Re-run Test in the modal after each change.