How to Whitelist DBEverywhere's IP Address

Most managed databases block connections from unknown IP addresses by default. Before you can connect through DBEverywhere, you need to add our static IP address to your database's firewall allow list.

Find the IP Address

DBEverywhere's current static IP is published on the IP Whitelisting page and is also shown on your dashboard next to each connection. All connections from DBEverywhere originate from this single IP address.

Why This Is Needed

When you connect through DBEverywhere, the connection to your database comes from our server, not your local machine. Your database firewall sees our server's IP. If that IP isn't on the allow list, the connection is refused before credentials are even checked.

Provider-Specific Instructions

DigitalOcean Managed Databases

1. Go to your database cluster in the DigitalOcean control panel.
2. Click Settings.
3. Under Trusted Sources, click Edit.
4. Add DBEverywhere's IP address.
5. Click Save.

AWS RDS

1. Open the EC2 Console and go to Security Groups.
2. Find the security group attached to your RDS instance.
3. Click Edit inbound rules.
4. Add a rule: Type = MySQL/Aurora (port 3306) or PostgreSQL (port 5432), Source = DBEverywhere's IP address with /32 suffix (e.g., 203.0.113.10/32).
5. Click Save rules.

Hetzner Cloud

1. Go to Firewalls in the Hetzner Cloud Console.
2. Select the firewall attached to your server.
3. Add an inbound rule allowing TCP on your database port (3306, 5432, etc.) from DBEverywhere's IP.
4. Apply the changes.

Generic / Self-Hosted

If you manage your own database server:

1. Open your database configuration file (e.g., my.cnf for MySQL, pg_hba.conf for PostgreSQL).
2. Ensure bind-address is set to 0.0.0.0 (not 127.0.0.1) so the database accepts remote connections.
3. Add a firewall rule (using ufw, iptables, or your cloud provider's firewall) allowing inbound TCP traffic on your database port from DBEverywhere's IP.
4. Restart the database service if you changed the bind address.

After Whitelisting

Once the IP is whitelisted, go back to DBEverywhere and try your connection again. The change usually takes effect within a few seconds for cloud providers.

If you're still getting "Connection failed" errors after whitelisting, double-check that you added the correct IP and that your database port matches what you entered in the connection form.