Hi! In my ISPConfig setup, the server is reporting its IP address as 127.0.1.1. Is this a configuration error? Should it be showing its public IP address instead, or could this be correct? If this is a misconfiguration, could it cause any issues? Thanks!
Did you set the hostname and /etc/hosts according to the installation guide? https://www.howtoforge.com/ispconfig-autoinstall-debian-ubuntu/ Where does it report 127.0.1.1?
Yes I did, and on that guide there is 127.0.1.1 server1.example.com server1 It's reported everywhere, also here: I also see that the gateway in my case is 0.0.0.0, sounds strange.
That correct there, this data is not in use. The option is not enabled and you should not use it when your interface is not called "eth0". Does your system work correctly?
Hi, I think I might have missed a step in the multi-server configuration. Specifically, the part where I should have added a line like: 10.0.0.12 server1.example.com server1 to the /etc/hosts file I've only just added this line to the /etc/hosts file on the master server. So, to correct this situation, do I just need to: Change the IP Address for server1.example.com in the ISPConfig Control Panel (under System > Server Config > server1.example.com) to its correct private IP (e.g., 10.0.0.12)? Ensure that the /etc/hosts file on (the server with IP 10.0.0.12) also contains the line 10.0.0.12 server1.example.com server1 (so it can resolve its own FQDN to its correct private IP)? Are these the main steps to fix it? Thanks!
No don't change any values here. As i already said this option is disabled. Correctly setup /etc/hosts, and the hostname on each server. After changing these configuration files a reboot is recommended.
also correctly set the ip's / hostnames of any other ispconfig servers in all the hosts files on all the servers. this'll ensure each server can connect to the master database / send alerts etc even if your dns gets messed up. also use the internal ip's of other hosts where they have their own private network rather than their public ip's. depending on your hosting, this'll avoid getting charged for traffic between ispconfig servers that might instead make its way to the network edge and then back in again.