Jakob Bouchard

Hey there, I just released 2.4.0, which added WP CLI support from jaap’s PR!

Hey! Sorry for the late reply, I’m quite busy with my new job and no longer in web development. I can look into adding wp-cli support, but I have no idea how it works, so it might take a while. If you do have any resources on it though, I’ll gladly take them and see if I can add the feature soon.

@bluesquares this is probably because the domain in hestia is entered as domain.com and https://www.domain.com is only an alias.

No problem ??

Can you try clearing your browser cache? The JavaScript changed quite a bit with the new update, maybe it’s loading incorrectly. If that fails, can you look if any error appear in the JavaScript console?

If you open the developer tools of your browser and go on the network tab, when you click on the button, you should see a request made to admin-ajax.php. If you click on it, and look at the response, is the success value set to true? And if not, there should be an error in the data it returned.

Yeah, I’ll be adding that! I agree, the button’s text is long. Maybe I could change it to just “Purge Hestia Cache” or “Purge Nginx Cache” instead too.

I never tried using WP Super Cache or similar with the plugin, however I’d assume it would be fine. I assume that NGINX would cache the files that WP Super Cache has generated, instead of directly what WordPress has generated.

However, I think that it’s unnecessary, because from my understanding, NGINX caches the HTML, CSS, JS, etc. that WordPress has generated. As far as I know, WP Super Cache does that too, except it uses Apache’s .htaccess file to configure caching. Maybe using something like Autoptimize could help with performance though, as this would defer JavaScript.

I might be wrong though.

• This reply was modified 2 years, 5 months ago by Jakob Bouchard.

You need to click on the profile icon in the top right corner of HestiaCP, then on the logs button. You should have entries with the API category saying something similar to
Access key xxxxxxxxxxxxxxxxxxxxx successfully launched with command v-purge-nginx-cache

Yeah I could definitely put that info somewhere. Perhaps in the Site Health page, in the Info tab.

• This reply was modified 2 years, 5 months ago by Jakob Bouchard.
• This reply was modified 2 years, 5 months ago by Jakob Bouchard. Reason: Formatting

Yes, changing this option will enable the caching. You can edit the default template in the packages! I’ve setup my default proxy template to be caching and my default backend template to use PHP 8.1

Yes, that’s the port I’m talking about ??

I actually updated the plugin to v2.0.0 a little earlier today with support for the new Hestia 1.6.0 API. I highly suggest you update to this version, as I also made an installation guide. Plus, it’s a more secure API, and I’ve removed a couple of bugs too.

Hey! It’s asking for the hestiacp port!

Hey! Sorry for the late reply, I didn’t get any notifications.

I just updated the plugin, so make sure to update your HestiaCP install to 1.6 and the plugin to 2.0.0, a lot of bugs have been fixed, and I have made an installation guide to help too.

Hey there! Sorry about the long reply time, I didn’t get any notification about the posts.

Indeed, it runs on Apache with a NGINX proxy, but you can enable the “caching” Proxy Template, in the advanced web settings. This will enable NGINX caching.

It needs the hestiacp port, yes. To check that it works, you can look in the user logs.