⭕Oracle Cloud / Amazon Lightsail: "bind cannot assign requested address 8025"

At first glance, this error can be misinterpreted to make you think it means a PORT is already in use.

What the error is telling you is that the IP ADDRESS you entered during installation can't be found in Ubuntu, because Oracle Cloud and Amazon Lightsail configure a different IP on your local VPS in the operating system than the IP they route to your VPS over the internet.

Your VPS has a hidden private IP address only you can see.

This is similar to how your home Wi-Fi network has a different IP network, commonly 192.168.0.x, which is proxied through your broadband internet router.

If you enter your public internet-facing IP address during installation, the ESP platform will fail to start since it has no knowledge of that IP.

Your VPS IP will be from one of the three private IP address ranges.

The following IP space is reserved for private networking and is non-routable on the internet: 10.0.0.0 to 10.255.255.255, 172.16.0.0 to 172.31.255.255, 192.168.0.0 to 192.168.255.255

For the ESP platform to start successfully, it needs to know the private IP address configured in Ubuntu, not the internet-facing IP address you used to connect to your server with SSH.

The easiest solution if you haven't done the installation already: When you're prompted for your IP address during installation just enter 0.0.0.0, this will cause the ESP platform to just start automatically on every IP address it can find.

You can't use the 0.0.0.0 method if you plan on using Velocity MTA on this server.

If you completed the installation and received the error on a failed startup:

You need to correct your configured IP address which is stored in the edcom-install/config/edcom.env file

View the contents of the file with the cat command:

cat config/edcom.env
PLATFORM_IP=1.2.3.4

You can do any of the following to correct this issue:

Method one

• Change PLATFORM_IP to 0.0.0.0 (Can't do this if running Velocity MTA on this server)

Use the 'nano' command to edit this file:

nano config/edcom.env

Method two

• Delete config/edcom.env with the rm command, which will cause 0.0.0.0 to be used automatically (Can't do this if running Velocity MTA on this server)

rm config/edcom.env

Method three

• Figure out what your private IP address is in Ubuntu and change PLATFORM_IP to that IP address

Use the ip command to see your private IP addresses:

ip a

Look for output similar to this:

You might also be shown your private IP addresses as part of the MOTD (message of the day) when you log in:

What to do when you have multiple private IP addresses on the same VPS

If you're planning on using Velocity MTA or any other applications on this VPS side by side with your ESP platform, you're going to need to know which public internet-facing IP address each of your private IP addresses is being proxied to.

Knowing the private IP to public IP mapping is necessary to make sure you configure your ESP platform to use the private IP address that links to the public IP you want to use for managing your ESP.

Use the 'curl' command to find your "real" IP by initiating a connection from your private IP to a compatible website that reveals your public IP:

# curl --interface 10.0.0.246 icanhazip.com 144.24.125.61 # curl --interface 10.0.0.128 icanhazip.com 144.24.125.186 # curl --interface 10.0.0.42 icanhazip.com 144.24.125.167 # curl --interface 10.0.0.231 icanhazip.com 144.24.125.150 # curl --interface 10.0.0.82 icanhazip.com 129.159.125.34

Restart the platform after you've made any changes toconfig/edcom.env

./restart.sh