Help
Blocked by the IP allow-list
Tested with:Databasezy API v1 · zb CLI 0.1
Each instance has an IP allow-list, on every plan including Free. The gateway checks your client’s public IP address against it before the TLS handshake. If the address is not on the list, the gateway closes the connection without sending any database error. Your driver reports a closed or reset connection, which is why allow-list problems are easy to mistake for network or TLS problems. Add the address your client really connects from, in CIDR form.
How to tell the allow-list is blocking you
Section titled “How to tell the allow-list is blocking you”- The connection closes immediately with
server closed the connection unexpectedly,SSL SYSCALL error: EOF detected,connection reset by peeror a TLS handshake failure, and no database error message. - It works from one machine or network and not from another.
- In the portal, open the instance and go to Network. The IP allow-list card shows “Your current address is not in the list” when the computer you are browsing from is not allowed, with an Add my address button. That checks your browser’s address; your application servers may use different addresses.
To see the current list from the CLI:
zb api GET /v1/orgs/{org}/instances/<instance_id>/networkWrite entries as CIDR blocks
Section titled “Write entries as CIDR blocks”Every entry needs a prefix length. A bare IP address is rejected with `203.0.113.7` is not a valid CIDR.
| You want to allow | Entry |
|---|---|
| One IPv4 address | 203.0.113.7/32 |
| An IPv4 range | 203.0.113.0/24 |
| One IPv6 address | 2001:db8::7/128 |
| Everyone (IPv4 and IPv6) | 0.0.0.0/0 and ::/0 |
The list holds 1 to 50 entries and cannot be empty. A new instance starts with 0.0.0.0/0 and ::/0, which allows
every address; the password and TLS still protect it.
Updating the list replaces it
Section titled “Updating the list replaces it”The API’s PUT replaces the whole list, so include the entries you want to keep:
zb api PUT /v1/orgs/{org}/instances/<instance_id>/network \ -d '{"allow_cidrs": ["203.0.113.0/24", "198.51.100.7/32"]}'Changing the allow-list needs permission to change the instance. If you turned on two-factor authentication, or your organization requires it, you may be asked to complete it first. Every change is recorded in the audit log. The gateway checks the list when a connection opens, so connections that are already open are not cut when you remove an address.
Label the ranges
Section titled “Label the ranges”In Network > IP allow-list, add an optional label with a new range, or choose its label to edit it. Labels such as Office or Production app servers help identify entries; they do not change who can connect. Use at most 120 characters. Leave a label empty to remove it.
The API returns labels in allow_cidr_labels, keyed by the exact range. Supply that map to replace labels;
omit it to keep labels for retained ranges. A removed range loses its label. The portal also sends the network’s
expected_revision; a concurrent change returns 409 and reloads the current settings instead of overwriting them.
IPv4 or IPv6?
Section titled “IPv4 or IPv6?”Your client may connect over IPv6 even if you expected IPv4, or the other way round. The portal says which one your browser used. If you are unsure, allow both of your addresses. Remember that an office or home address can change. For an IPv4-only endpoint, including the current single-IP cell, add your database client’s public IPv4 address: an IPv6 entry does not permit an IPv4 connection or add IPv6 connectivity.
Serverless and platform egress addresses
Section titled “Serverless and platform egress addresses”Serverless functions and many hosting platforms do not use fixed outbound addresses. You have two options:
- Give the platform a fixed address. Use its static egress or NAT feature and allow that address. Each platform guide says where to find it: for example a NAT gateway for AWS Lambda and Cloud Run, or static outbound IPs on Railway and Render.
- Allow everyone with
0.0.0.0/0and::/0, and rely on TLS and a strong, rotated password. The portal shows a warning while the instance accepts any address.
Cloud providers publish their address ranges, but they are large and change. Prefer a fixed egress address.
Migrations
Section titled “Migrations”- A migration into Databasezy connects out from our side to your source, so it is your source’s firewall that must allow us, not this allow-list. See Before you migrate.
- Reverse sync after a PostgreSQL cutover is the other way round: your old source connects to the instance, so its address must be on the instance’s allow-list.
Still stuck?
Section titled “Still stuck?”Search the help center or ask the assistant in the portal Help panel. If that does not solve it, open a support ticket
from the portal (Help → Open a ticket). Include the instance id, the region, the public IP address your client
connects from (for example from curl https://ifconfig.me on that machine), the exact error text, your client or
driver version, and the time it happened in UTC. Never paste passwords, connection strings with passwords, API keys
or patient data (PHI) into a ticket. See How to get help.