MultiConnectMultiConnectDocs Website home
MultiConnectCloud › Database Deployments

5. Choose who can connect

A database refuses every connection except from the addresses you list. That is the opposite of most defaults, and it is deliberate: an open database port is found by automated scanners within minutes.

To change the list, open your project on the dashboard, then the deployment, and use the Network Access section:

  1. Type an address or range, such as 203.0.113.24 or 198.51.100.0/24, and select Add.
  2. To remove one, select the cross on it.
  3. Select Save.

The list you see when you select Save becomes the whole list. Changes take effect within seconds, with nothing to restart.

Entry How it is saved
A single IPv4 address, such as 203.0.113.24 203.0.113.24/32, just that machine
A single IPv6 address /128, just that machine
A range, such as 198.51.100.0/24 As typed. The prefix must be 0 to 32 for IPv4, or 0 to 128 for IPv6

Add the public address your application connects from. That is your server's outgoing internet address, not your laptop's and not a private address inside your network. Behind NAT, it is the NAT gateway's address. To find it, run this on the machine that will connect:

Script 5.1: Find the address a machine connects from

curl -s https://api.ipify.org

Add the result as a single address.

Toggle What it does
Allow linked API deployments Lets in API deployments on MultiConnectCloud that are linked to this database, even as they move to new machines. See Section 7

MultiConnectCloud's own systems can always reach the database, so it keeps running whatever is in your list. They are never shown in the list and cannot be removed.

The cache add-on is protected by the same list.