I can’t connect to the host from DollarDeploy

Your provider may limit who can access the server via SSH.

The same applies to your cloud provider account. Some providers let you limit an API key to specific IP addresses, and every provider offers a cloud firewall that can block SSH. If DollarDeploy is not on those lists, connecting the provider or reaching the server fails. See Cloud provider access below for each supported provider.

Yes, this is a common pattern for increasing security. While many people find it not sufficient to eliminate threats from sophisticated actors, it is an initial level of defense that is good to have.

To allow access, add DollarDeploy IP address to the list of IP addresses allowed to access your server via SSH:

DollarDeploy IP addresses

Current (5.1.2026): 77.42.41.205, 95.216.181.135
IPv6 (26.10.2026): 2a01:4f9:c010:9158::/64
Previous (14.6.2025): 63.33.71.230
Previous (1.08.2024): 3.252.97.186

DollarDeploy connects to cloud provider APIs over IPv6 when available, so an allow list with only IPv4 addresses is not enough.

We will update the page as our infrastructure scales or changes.

Firewall settings

If you have configured a firewall on your server, make sure DollarDeploy can connect. Allow access from our IP address:

ufw allow from 95.216.181.135

Cloud provider access

DollarDeploy talks to your provider in two ways: it calls the provider API with your key to create and manage servers, and it connects to the servers over SSH (port 22). Allow these addresses wherever your provider restricts access:

• API allow lists: 77.42.41.205/32, 95.216.181.135/32, 2a01:4f9:c010:9158::/64
• SSH (cloud firewall, security group): 77.42.41.205/32, 95.216.181.135/32

Include the IPv6 subnet in API allow lists. DollarDeploy reaches provider APIs over IPv6 when the provider supports it, so a list with only the IPv4 addresses can still fail.

DigitalOcean

• API: you connect with DigitalOcean OAuth, so there is no API allow list to configure.
• SSH: if a Cloud Firewall is attached to the droplet (Networking -> Firewalls), add an inbound rule for SSH (TCP 22) from both IPv4 addresses.

Hetzner

• API: Hetzner Cloud API tokens are not limited by IP address, nothing to configure.
• SSH: if a Hetzner Cloud Firewall is applied to the server (Firewalls in the project), add an inbound rule for TCP port 22 from both IPv4 addresses.

Vultr

• API: Vultr can restrict which IP addresses may use an API key. If the restriction is on and DollarDeploy is not on the list, Vultr rejects every request with Unauthorized IP address and DollarDeploy shows the key as rejected, even though the key is correct. To fix it:

  1. Open the Vultr dashboard and go to Manage User -> API Access.
  2. In Access Control, add each address as a subnet and click Add: 77.42.41.205 + prefix 32, 95.216.181.135 + prefix 32, 2a01:4f9:c010:9158:: + prefix 64.
  3. Go back to DollarDeploy and paste the API key again.

  Allow All IPv4 and Allow All IPv6 in the same screen remove the restriction entirely. This works, but then anyone who gets your key can use it from anywhere, so we recommend adding our addresses instead.

• SSH: if a Firewall Group is linked to the instance (Network -> Firewall), add an inbound SSH (TCP 22) rule from both IPv4 addresses.

Verda (formerly DataCrunch)

• API: if your organization restricts Verda API access by IP address, allow all three addresses for the Client ID you use with DollarDeploy.
• SSH: if you restrict inbound traffic to the instance, allow TCP port 22 from both IPv4 addresses.

AWS

• API: if the IAM policy for the DollarDeploy access key uses an aws:SourceIp condition, add all three addresses to it, otherwise AWS answers with an access denied error. See Start with AWS for the policy we need.
• SSH: the instance security group needs an inbound rule for SSH (TCP 22) from 77.42.41.205/32 and 95.216.181.135/32.

Backup storage (S3-compatible)

DollarDeploy tests the bucket and signs backup requests, and your servers upload and download the backup files themselves. If the bucket policy limits access by IP address (for example with aws:SourceIp), allow all three DollarDeploy addresses and the public IP addresses of your servers.

GitHub

If your GitHub organization uses an IP allow list (Settings -> Authentication security -> IP allow list), add all three DollarDeploy addresses, otherwise DollarDeploy can not list repositories or fetch code for your apps.

Error messages

When a provider rejects the key, DollarDeploy shows the reason the provider gave, for example Unauthorized IP address: ... from Vultr. If the message mentions an IP address, the allow list is the cause, not the key.