Hi,
on one DirectAdmin installation only, the IP the system is using for outbound connections is not the server IP, but an extra IP we have added.
For example using this command:
The extra IP was added using DirectAdmin (IP management). It is a "shared" IP assigned to a reseller. The IP was added to the same one and only interface as the main IP.
This extra IP is not showing in "ifconfig" output (as expected).
Note: This is the only DirectAdmin installation on RHEL8 based Linux (AlmaLinux in particularly). We run more DirectAdmin systems on CentOS7 where we always get the server IP for outbound connections there, correctly, as expected.
Does anyone know why we don't get the server IP here by default?
Is there any way we can have the system IP without firewall manipulations?
Thank you very much.
on one DirectAdmin installation only, the IP the system is using for outbound connections is not the server IP, but an extra IP we have added.
For example using this command:
the IP shown is not the server IP, but the extra IP.wget --tries=1 -qO - http://myip.directadmin.com
The extra IP was added using DirectAdmin (IP management). It is a "shared" IP assigned to a reseller. The IP was added to the same one and only interface as the main IP.
This extra IP is not showing in "ifconfig" output (as expected).
Note: This is the only DirectAdmin installation on RHEL8 based Linux (AlmaLinux in particularly). We run more DirectAdmin systems on CentOS7 where we always get the server IP for outbound connections there, correctly, as expected.
Does anyone know why we don't get the server IP here by default?
Is there any way we can have the system IP without firewall manipulations?
Thank you very much.
Last edited: