Hello I have the following problem. The websites all go offline after about a day although Apache and Mysql are running. You can still get into the panel and everything looks fine.
Yesterday the server was restarted and the websites still stayed offline. After 30 minutes without doing anything everything went online again.
The problem occurs now only after I updated Hestiacp from 1.2.4 to 1.3.2.
Another error I found in Hestia SSL at ISSUER: C = US, ST = California, L = San Francisco, O = Hestia Control Panel, OU = IT, CN = server.domain2.com, emailAddress =
Suddenly there is another domain in here. “Server.” is correct but domain2.com is not correct. Why did this change? I do not know since when the change is in the domain also runs on the server but has nothing to do with the panel. If the server crashes because of this I can’t say.
Sat Jan 09 15:38:18.677721 2021] [mpm_prefork:error] [pid 1128] AH00161: server reached MaxRequestWorkers setting, consider raising the MaxRequestWorkers setting
And one more error I just found:
in error_reporting the following is entered:
E_ALL |E_ALL |E_ALL |E_ALL & ~E_DEPRECATED & ~E_STRICT& ~E_DEPRECATED & ~E_STRICT& ~E_DEPRECATED & ~E_STRICT& ~E_DEPRECATED & ~E_STRICT
I doubt that I have written so many E_ALL myself. Something is stored twice.
You can’t downgrade to a lower hestia version, this isnt supported. Also as @eris already pointed out, there were no changes from 1.2.4 to 1.3.2 for apache2. What do you run exactly? Apache2+Nginx?
As @eris also pointed out is that you’re still running on mpm_prefork - fpm has a much better performance and is since 1.1.1 (!) the default for any new hestia installation. Please consider to run the manual migration script, you’ll find the needed informations here: Getting Started | Hestia Control Panel
No idea about your other point about the “new” domain, hestia doesnt change anything automatically .
at the moment the server runs without problems. but i haven’t switched to Mpm event yet. however i have set the max_execution_time to 120, before it was unlimited.
That would explain a lot - unlimited execution time would overload the server on bad written scripts. Glad you found it out, even when “unlimited” isnt hestia’s default value .