What exactly ‘Cache duration’ under a domain is (FastCGI), and how it works?
Is there any working plugin for wordpress that works without changing bunch of files on the server side, that would only require API credentials and per domain?
I found this one, but it doesn’t seem to work at all.
If anyone knows what to change inside, for it to work properly, can you drop changes here, and show us what needs to be done for it to work properly?
I find docs very confusing:
v-delete-fastcgi-cache
Disable FastCGI cache for nginx
Does it delete cache, or disables caching for a certain domain?
Cache duration = Time (m/h/d) untill the page is cached again.
Is there any working plugin for wordpress that works without changing bunch of files on the server side, that would only require API credentials and per domain?
I found this one , but it doesn’t seem to work at all.
Last time I tested the plugin worked fine. Make sure your public ip is in the Server settings → Security → API white list
Disables the cache for that domain
Purge / deletes the cache (Or proxy cache if your are using Nginx as proxy)
Ok, done that. But I still can’t figure why it’s not working. All my pages after purging cache are still HIT.
I guess I should see a response in config/logs, just like when I purge cache manually from CP.
Tried with button on admin bar, it only goes blue, without any response.
Tried making new post, updating old post, nothing.
Is there some exotic settings where PHP and NGINX have to be same user?
Or maybe my default settings are not meant for it?
Well, I’ve copied that part from nginx.conf
Since I have two folders inside /var/cache/nginx/micro for both of my domains, i guess it’s properly configured, except the part max size, which is custom.
Maybe I’ve messed up something when entering data on configuration page, because I’ve misunderstand what needs to be the input.
Host - subdomain.domain.tld where my Hestia panel is (without https://) ?
port - 8083 if I use that one for HestiaCP
API key - that was the most documented part, and it’s the only part I’m 100% sure it’s correct
Hestia user - obviously user that’s having that domain under his name in HestiaCP