How can I test it?

Same question.

Does a WordPress site created via Hestia even use NGINX? Looks like Apache to me.

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.

@jakobbouchard thanks for that informative reply.

Are you suggesting simply changing this option and pressing “Save” will enable caching on my WordPress site?

If so, great but I’m a bit confused as to why this isn’t the default when creating a WordPress site.

It needs the hestiacp port, yes

Just to be double-sure, you mean the port at the end of the Hestia URL e.g. https://hcp.domain.com:2083/?

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.

Fantastic thank you @jakobbouchard. I’ve followed your new guide with Hestia 1.6.0.

Final question (sorry!) to verify this plugin is working correctly you mention the “user logs”. Could you be a bit more specific about where in Hestia to find these and verify correct behaviour?

I suppose longer term it would be nice if the plugin gave some indication that it was connected/setup correctly. The “Redis Object Cache” plugin displays this information like this for e.g.

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

You should have entries with the API category

Thank you, I’ve confirmed these are appearing ??

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

Yeah, or just something simple on the settings page. The only other feedback I have re: this plugin is permanent items in the Admin Bar can be a bit annoying, and “Purge Hestia Nginx Cache” is quite long. It would be nice of there was an option to disable this Admin Bar item in the plugin settings, and a button to flush the cache there too.

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.

@alecrust Redis cacche will still help speeding up the backend and for logged in users as by default the cacheing is disabled for logged in users