I paused the site 5 hours ago as i was doing some changes.
I enabled it again, its working on my side and for other people,
But a very few users see this error,
I suspect there is some cache or something? Did it happen to someone before and how to solve it?
Ask them to change the DNS which may still be using cached site (if they are using any DNS).
But first try and clear site data and cookies and reload. Try with CTRL+SHIFT+R in most browsers and it should help.
But I didn’t change IP or DNS records, how will (him) changing the DNS in his device solve the issue?
Also My website is behind cloudflare I tried to do “Purge cache” didnt help
Show the output of this command and we will see whether the web domain is really suspended (replace HereYourDomain with the actual domain name):
cat /etc/nginx/conf.d/domains/HereYourDomain.conf
cat /etc/nginx/conf.d/domains/[REDACTED].conf
[REDACTED on 2026-02-16]
In any case, I restarted the whole VPS now,
I think it was fixed byitself!
It looks like the issue was due to caching on the client side.
When a site is suspended in Hestia, the web template is changed and the root directive points to /usr/local/hestia/data/templates/web/suspend:
root /usr/local/hestia/data/templates/web/suspend;
It looks like the issue was due to caching on the client side.
I suggest, that whe hestia adds that link it should also add Caching headers below it that force browser to NEVER cache the response, what do you think?
When Hestia suspends a site, it only changes the root directive. It has no knowledge of which template the site is using (there are tons of templates and users may have modified existing ones or added new ones), so attempting to modify an arbitrary template could lead to even worse issues.
It has no knowledge of which template
hmm am thinking what’s inside the /usr/local/hestia/data/templates/web/suspend ?
if it’s a index.php script then you can simply add a header() line there with to disable the cache.
It’s an index.html file.