Hello to everyone. I have added one more IP address directly to ISPConfig console and after reboot system it is not working. I need help with fixing this and I don't know where is the problem. Thank you in advance !
We do not know what you did i.e. in details of how you add the said IP and we definitely cannot read minds, so please read this before posting: https://www.howtoforge.com/community/threads/please-read-before-posting.58408/
Sorry for my mistake. I have successfully installed ISPConfig 3 on Debian. My VPS was with 1 IP and after a week, I have bought second one IP address. After that I have added the second one IP into ISPConfig API. Now I don't have ISPConfig panel and also my websites are not running.
You already told us you added the new ip but how did you add it? Please explain step by step. And please do what is needed as advised in the above given link.
under Admin login : 1. Click on System 2. Server IP Addresses 3. add new IP address. 4. Save 5. Reboot system via ssh Here is the log : Code: ##### SERVER ##### IP-address (as per hostname): ***.***.***.*** [WARN] could not determine server's ip address by ifconfig [INFO] OS version is Debian GNU/Linux 10 (buster) [INFO] uptime: 00:48:35 up 1:12, 2 users, load average: 0.00, 0.00, 0.00 [INFO] memory: total used free shared buff/cache available Mem: 5.8Gi 468Mi 5.0Gi 20Mi 340Mi 5.1Gi Swap: 2.0Gi 0B 2.0Gi [INFO] ISPConfig is installed. ##### ISPCONFIG ##### ISPConfig version is 3.2.7p1 ##### VERSION CHECK ##### [INFO] php (cli) version is 7.3.33-1+0~20211119.91+debian10~1.gbp618351 [INFO] php-cgi (used for cgi php in default vhost!) is version 7.3.33 ##### PORT CHECK ##### [WARN] Port 8080 (ISPConfig) seems NOT to be listening [WARN] Port 8081 (ISPConfig Apps) seems NOT to be listening [WARN] Port 443 (Webserver SSL) seems NOT to be listening ##### MAIL SERVER CHECK ##### ##### RUNNING SERVER PROCESSES ##### [INFO] I found the following web server(s): Apache 2 (PID 1332) [INFO] I found the following mail server(s): Postfix (PID 802) [INFO] I found the following pop3 server(s): Dovecot (PID 479) [INFO] I found the following imap server(s): Dovecot (PID 479) [INFO] I found the following ftp server(s): PureFTP (PID 1597) ##### LISTENING PORTS ##### (only () Local (Address) [anywhere]:993 (479/dovecot) [anywhere]:995 (479/dovecot) [localhost]:10023 (621/postgrey) [localhost]:10024 (889/amavisd-new) [localhost]:10025 (802/master) [localhost]:10026 (889/amavisd-new) [localhost]:10027 (802/master) [anywhere]:587 (802/master) [anywhere]:110 (479/dovecot) [anywhere]:143 (479/dovecot) [anywhere]:465 (802/master) [anywhere]:21 (1597/pure-ftpd) ***.***.***.***:53 (492/named) [localhost]:53 (492/named) [anywhere]:22 (487/sshd) [anywhere]:25 (802/master) [localhost]:953 (492/named) *:*:*:*::*:993 (479/dovecot) *:*:*:*::*:995 (479/dovecot) *:*:*:*::*:10023 (621/postgrey) *:*:*:*::*:10024 (889/amavisd-new) *:*:*:*::*:10026 (889/amavisd-new) *:*:*:*::*:3306 (598/mysqld) *:*:*:*::*:587 (802/master) [localhost]10 (479/dovecot) [localhost]43 (479/dovecot) *:*:*:*::*:80 (1332/apache2) *:*:*:*::*:465 (802/master) *:*:*:*::*:21 (1597/pure-ftpd) *:*:*:*::*:53 (492/named) *:*:*:*::*:22 (487/sshd) *:*:*:*::*:25 (802/master) *:*:*:*::*:953 (492/named) ##### IPTABLES ##### Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination ##### LET'S ENCRYPT ##### acme.sh is installed in /root/.acme.sh/acme.sh
Basically if the new ip address is a working ip and set to your server properly, there should be no problem. I add However, did you properly add the new ip address to your vps in your hosts file, at your vps provider settings and dns settings? Can the new ip address truly reach your server via browser and terminal? Can the old ip address still reach your server via browser and terminal?
You can check your server ip via terminal command "ip a" and see whether the new ip is already set together with the old ip. The file is /etc/hosts which normally has the ip of your server e.g. xxx.xxx.xxx.xxx server1.domain.tld but this may or may not necessarily be required by your vps. And depending on whether you use network or netplan, I believe it should be added in there too. Netplan config file should be in /etc/netplan/ and while network is /etc/network/interfaces. Again this may or may not necessarily be required by your vps, as some vps just require you to only set them in the your vps provider settings.