I can confirm the fix above seems to work. Not sure why at the moment, but its good enough to get things moving again.
Have checked a few other hestia servers. Seems like most of them are OK. Currently only 1 out of 6 that has been affected. Unsure why
All your servers are on same OS? Debían? Same Hestia panel version?
Mine failed 2 of 2 after the upgrade and both fixed the same way.
I’m wondering if, in your case, not all the servers failed, if there is any stray corrupted .htaccess somewhere and my line overwrite it.
My test server have only few domains and also failed. It’s like apache2 not reading domain template in Hestia since there is a “AllowOverride All” line, but I guess isn’t as safe as None.
Servers a mix of Ubuntu 20 and 22. It failed on a 20.4 version.
Still can’t understand why this happened. No apparent upgrade to Apache or change in config.
Tried removing .htaccess entirely from one affected domain, but still the same error. So don’t think it was anything in there. Tried commenting out various IfModules. No effect there. Very strange.
One domain did stay up. That didn’t use apache, i.e used an nginx template proxying to a node app running on an unexposed port.
How can I check this exactly? I have turned off proxy mode for all domains. But only after I moved the templates files, the domains were running again. Except for the webmail address. It is still not working. I can DM you the conf of the webmail and one of the other domains if that helps.
I am having the same problem, I tried both the changes that Maxi suggeted but it does not work still, I cannot get into hcp or my domain. any more ideas please?
It seems my problem is with the DNS records, if I add it to the hosts file on my PC it works, for some reason it is not propagating so I will look into that.
@Clive are your nameservers registered with your registrar, I know i had a problem with propagation and it was due to the registrar not have my nameserver IPs correct or registered.