When using Ploi to manage your servers and deploy applications, you may need to whitelist our IP addresses in your security configurations, firewalls, or other access control systems. This guide provides all the necessary IP addresses you'll need and explains the required ports for proper communication.

Worker server IP addresses

These are the main IP addresses used by Ploi's worker servers to deploy and manage your applications:

• 🇳🇱 -Hidden- - Web server

• 🇳🇱 -Hidden- - Amsterdam worker

• 🇳🇱 -Hidden- - Amsterdam worker

• 🇩🇪 -Hidden- - Frankfurt worker

Uptime monitoring server IP addresses

Ploi's uptime monitoring service uses the following IP addresses to check your site's availability:

• 🇬🇧 London: 94.237.51.22

• 🇺🇸 Chicago: 209.50.49.15

• 🇸🇬 Singapore: 95.111.198.27

Having monitoring servers in multiple geographic locations allows us to detect region-specific outages and provide more accurate uptime reporting.

Required ports for Ploi access

SSH access (port 22)

Ploi requires SSH access (port 22) to your servers to perform:

• Initial server provisioning

• Server management operations

• Application deployment

• Script execution

• Package installation and updates

• Service management (restart, stop, start)

If your server uses a custom SSH port instead of the default port 22, you'll need to specify this port in your Ploi server configuration.

How to whitelist Ploi IPs

You can easily do that by going to the network tab in Ploi (in your server) and whitelist the worker IP's listed above.

However, if you'd like to do it manually, you can also do that:

sudo ufw allow from -Hidden- to any port 22 proto tcp
sudo ufw allow from -Hidden- to any port 22 proto tcp
# Repeat for all Ploi IPs

Cloud provider security groups

Most cloud platforms (AWS, DigitalOcean, Linode, etc.) allow you to configure security groups or network rules. Add inbound rules for the Ploi IP addresses to ports 22, 80, and 443.

Troubleshooting connection issues

If Ploi cannot connect to your server after whitelisting:

1. Verify that the correct IP addresses were added to your whitelist

2. Check that port 22 (or your custom SSH port) is open for these IPs

3. Ensure your SSH service is running (sudo systemctl status sshd)

4. Check your server's firewall logs for blocked connection attempts

5. Verify network/cloud provider firewall settings

For further assistance with IP whitelisting or connection issues, please contact our support team.

IP changes

We try to prevent adding/changing IP's as much as possible. If we do have an IP change or a new IP, we will be sending you an email in time notifying you about this in time.