The admin panel is working properly no problems but all websites do not load unless restart apache2. Also after restart it apache2 is running but websites do not load. I am using Letsencrypt for SSL. Please advice what to look for all help appreciated.
Check that the websites are not disabled in ISPConfig, probably the active checkbox is not ticked. You might have enabled traffic quota in the website settings. When the quota is exceeded, then websites get disabled. In this case, enable the site again and ensure to set a proper traffic quota or set the traffic quota to its default, which is -1, to disable traffic quota.
Hard disk quota does not matter here; it's the traffic quota that can disable a site. If that's at -1 and the active checkbox is ticked, then you have a different kind of issue. Which exact error message do you get and how long does it take until websites stop working (a few minutes, hours, days, months)?
There are no errors. It was working fine yesterday just that the server got slow so rebooted it and all stopped working. After restart it would work for a few refresh and then stops. Apache is running but all sites except one would not load. Then restart apache it would run but after a few refreshes it stops. but one sites runs normally. This is part of the system log 2026-06-23T17:29:03.182501+02:00 chrisisp systemd[1]: apache2.service: Killing process 15857 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.182998+02:00 chrisisp systemd[1]: apache2.service: Killing process 15992 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183301+02:00 chrisisp systemd[1]: apache2.service: Killing process 16465 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183354+02:00 chrisisp systemd[1]: apache2.service: Killing process 16466 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183482+02:00 chrisisp systemd[1]: apache2.service: Failed to kill control group /system.slice/apache2.service, ignoring: Invalid argument 2026-06-23T17:29:03.183514+02:00 chrisisp systemd[1]: apache2.service: Killing process 15600 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183547+02:00 chrisisp systemd[1]: apache2.service: Killing process 15830 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183576+02:00 chrisisp systemd[1]: apache2.service: Killing process 15831 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183601+02:00 chrisisp systemd[1]: apache2.service: Killing process 16465 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183625+02:00 chrisisp systemd[1]: apache2.service: Killing process 16466 (php-cgi) with signal SIGKILL. 2026-06-23T17:29:03.183649+02:00 chrisisp systemd[1]: apache2.service: Killing process 15658 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183676+02:00 chrisisp systemd[1]: apache2.service: Killing process 15777 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183717+02:00 chrisisp systemd[1]: apache2.service: Killing process 15856 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183749+02:00 chrisisp systemd[1]: apache2.service: Killing process 15857 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183777+02:00 chrisisp systemd[1]: apache2.service: Killing process 15992 (apache2) with signal SIGKILL. 2026-06-23T17:29:03.183879+02:00 chrisisp systemd[1]: apache2.service: Failed to kill control group /system.slice/apache2.service, ignoring: Invalid argument 2026-06-23T17:29:03.183907+02:00 chrisisp systemd[1]: apache2.service: Deactivated successfully. 2026-06-23T17:29:03.183933+02:00 chrisisp systemd[1]: apache2.service: Unit process 15600 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.183962+02:00 chrisisp systemd[1]: apache2.service: Unit process 15830 (php-cgi) remains running after unit stopped. 2026-06-23T17:29:03.183987+02:00 chrisisp systemd[1]: apache2.service: Unit process 15831 (php-cgi) remains running after unit stopped. 2026-06-23T17:29:03.184011+02:00 chrisisp systemd[1]: apache2.service: Unit process 16465 (php-cgi) remains running after unit stopped. 2026-06-23T17:29:03.184035+02:00 chrisisp systemd[1]: apache2.service: Unit process 16466 (php-cgi) remains running after unit stopped. 2026-06-23T17:29:03.184060+02:00 chrisisp systemd[1]: apache2.service: Unit process 15658 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.184088+02:00 chrisisp systemd[1]: apache2.service: Unit process 15777 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.184113+02:00 chrisisp systemd[1]: apache2.service: Unit process 15856 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.184137+02:00 chrisisp systemd[1]: apache2.service: Unit process 15857 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.184164+02:00 chrisisp systemd[1]: apache2.service: Unit process 15992 (apache2) remains running after unit stopped. 2026-06-23T17:29:03.184365+02:00 chrisisp systemd[1]: Stopped apache2.service - The Apache HTTP Server. 2026-06-23T17:29:03.184458+02:00 chrisisp systemd[1]: apache2.service: Consumed 6.415s CPU time, 195.2M memory peak, 0B memory swap peak. 2026-06-23T17:29:03.188352+02:00 chrisisp systemd[1]: apache2.service: Found left-over process 15777 (apache2) in control group while starting unit. Ignoring. 2026-06-23T17:29:03.188400+02:00 chrisisp systemd[1]: apache2.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 2026-06-23T17:29:03.188428+02:00 chrisisp systemd[1]: apache2.service: Found left-over process 15857 (apache2) in control group while starting unit. Ignoring. 2026-06-23T17:29:03.188453+02:00 chrisisp systemd[1]: apache2.service: This usually indicates unclean termination of a previous run, or service implementation deficiencies. 2026-06-23T17:29:03.202270+02:00 chrisisp systemd[1]: Starting apache2.service - The Apache HTTP Server... 2026-06-23T17:29:03.218532+02:00 chrisisp apachectl[16795]: AH00548: NameVirtualHost has no effect and will be removed in the next release /etc/apache2/sites-enabled/000-ispconfig.vhost:7 2026-06-23T17:29:03.284634+02:00 chrisisp systemd[1]: Started apache2.service - The Apache HTTP Server.
Have you checked the load of your system and memory usage using top command? Might be just a DOS attack, or your system runs out of memory.
Try finding out what is happening. There is a reason apache processes get killed. Use for example commands htop, jnettop, iotop.
I think I found the reason apache was dying because of the threads were too low. Not sure if editing the conf directly was smart but it worked out in the end
