After setting up a second ispconfig and linking it to the primary ispconfig, the secondary dns is working. Unfortunately the ufw firewall is disabled. Enabled ufw by cmd but it does not obey the settings in ispconfig. For now I have manually set ufw using 'ufw allow 53/udp' and 'ufw allow 22/tcp' and so on. I have set the system>system config to debug and saved. Then went to /var/log/ispconfig/ and did a 'tail -F ispconfig.log' to see if some command would call ufw but the logs are empty. Completely empty. What else should I do to get the ufw to obey ispconfig? It looks like non of the actions done on ispconfig is going to the job queue. There is no red dot. Like when I activated let's encrypt for a site, no red dot. What can I check?
Please check if there is a link for firewall_plugin.inc.php in /usr/local/ispconfig/server/plugins-enabled/ folder.
The link is there. Code: lrwxrwxrwx 1 root root 69 Jul 29 23:50 firewall_plugin.inc.php -> /usr/local/ispconfig/server/plugins-available/firewall_plugin.inc.php Is there another thing to check? Here is cron lines just in case. Code: 57 8 * * * "/root/.acme.sh"/acme.sh --cron --home "/root/.acme.sh" > /dev/null * * * * * /usr/local/ispconfig/server/server.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done * * * * * /usr/local/ispconfig/server/cron.sh 2>&1 | while read line; do echo `/bin/date` "$line" >> /var/log/ispconfig/cron.log; done 0 0 * * * /usr/local/ispconfig/server/scripts/create_daily_nginx_access_logs.sh &> /dev/null There are logs lines in the acme.log and cron.log. ispconfig.log is empty. Hope these help to find the issue.
Yes that is correct. It was set to ufw. The server is Debian 12. Please take note, the red dot does not even appear when on a website that was set to "Let's Encrypt SSL". So it looks like every action does not trigger a job queue. Even when I changed the System > Server Config > Server > Loglevel to Debug. There is no red dot.
Unfortunately, there is nothing listed in Monitor > Jobqueue There is stuff listed in Monitor > Datalog History It shows the actions I have done. Like turning on the firewall and ssl for a website.
I wonder if you maybe reused the master database for the slave server or something like that during setup? The new slave server has its own local MySQL database; it is not using the master database? Slave nodes are just connected to the master database using master database settings in config.inc.php; they must always have their own local MySQL server and database.
I do not think I did that. I will reinstall everything again and follow the documentation. I have already done this two times. Maybe I need to delete the link to the secondary in the primary ispconfig. I did see two links to the same secondary in the primary. I will try again.
Ok, if you reinstalled without removing the system completely from master, then you have a system there that is stuck. Please ensure to completely delete the slave node from the master server under System > server services.
I think that was my mistake. This time I will make sure I remove the secondary from the primary before doing the reinstall.
Found my mistake. Me trying to be too smart. Now I think I understand how to use multiserver ispconfig. All actions must be done in the primary. That's the way it should be after all anyway! The secondary just obeys the primary. In all actions, not just the DNS. Even email and web setup. That is why web interface to ispconfig should not be installed on the secondary. My error was I installed the web interface to ispconfig in the secondary server. And I was loging into the secondary using the web interface. Which I should not! Is there a way for me to remove the web interface without breaking the secondary ispconfig? Or I should just leave it there for some checking or admin purpose? Or I should reinstall again?
