⚠️Common installation issues
Make sure new IPs are configured on your server, not just provisioned to your server.
When your server hosting provider provisions you more IPs, someone has to enable them in Ubuntu in order for the MTA to be able to access them.
New IPs won't "just work" on your server.
Your server hosting provider most likely didn't touch your server at all, all they did was give your server access to more IPs on the network than it had access to before, and now someone has to tell your server what those IPs are.
ChatGPT can tell you exactly what to do here, or you can try opening a ticket with your hosting provider and see if they will do it for you.
If all else fails there's Fiverr.
Don't ask us, we'll just ask ChatGPT and tell you what that dude said.
Seriously though, we can't do IT related things on your servers and be responsible for them and all the ways we will screw it up just as much as anyone else is going to. You should screw it up yourself, we believe in you 👍.
This is what's going to happen when you start Velocity MTA and your IP addresses aren't configured in Ubuntu:
:PANIC::: listen tcp 1.2.3.4:25 Bind: cannot assign requested address
This means the IP addresses aren't configured on your server, but you put the IP addresses in conf/ipaddresses, and Velocity MTA can't see them, so it's throwing an error and crashing.
In order for Velocity MTA to start, all of these files need to exist
If any of these files are missing, Velocity MTA will crash with ugly error messages:
conf/ipaddresses
conf/receiving_domains
conf/mta.conf
Bind: address already in use
Port 25 or Port 80 are being blocked by another application sharing this IP address
If ports required for Velocity MTA to start are being blocked by another application on the server, you'll see error messages like this and it will fail:
Velocity MTA must be installed on its own IP address and can not share an IP with other applications that may cause port conflicts.
Ports needed by Velocity MTA include ports 25, 80, and 81, if any these ports are blocked and unavailable, the platform will fail to start.
These are common scenarios where another application using the same IP address as Velocity MTA is blocking ports 25 or 80:
You're running the ESP platform on the same server as Velocity MTA and trying to use the same IP address for both applications. The ESP platform and Velocity MTA must use two different IP addresses in order to share the same server.
The Linux installation you're using came with Postfix out of the box or you have another MTA running such as PowerMTA which is blocking port 25.
You have some type of control panel software the server came pre-installed with such as CloudPanel, CPanel, or Plesk blocking port 80.
You're running a web-based application on the server that isn't necessarily a website but is still accessed using http:// in a web browser.
Last updated