Is the $no_cache variable and wp cooke and session section of the nginx.conf not set up fully? On a default install they don’t do anything, and looking in the confs it doesn’t look like everything needed is there?
Also I can’t seem to override this part of the conf for /wp-admin/ Like nothing has worked…
location / {https://xxxxxxxx @fallback ;
eris
July 20, 2020, 11:03pm
2
Currently I am using the following template the cacheing template found in /usr/local/hestia/data/templates/web/nginx/
For me it works fine on a heavy wordpress site.
The no cache part:
location / {
proxy_pass http://%ip%:%web_port%;
proxy_cache cache;
proxy_cache_valid 15m;
proxy_cache_valid 404 1m;
proxy_no_cache $no_cache;
proxy_cache_bypass $no_cache;
proxy_cache_bypass $cookie_session $http_x_update;
location ~* ^.+\.(%proxy_extentions%)$ {
proxy_cache off;
root %docroot%;
access_log /var/log/%web_system%/domains/%domain%.log combined;
access_log /var/log/%web_system%/domains/%domain%.bytes bytes;
expires 1h;
try_files $uri @fallback;
}
}
I had to stop using the caching template cause it aggressively cached my wp admin
that block is setting cache control headers for a year on wordpress admin. I tried to override it but i can only get the page not the assets to change
eris
July 21, 2020, 5:47am
5
Assets are not chanced due to the log expires time.
Decrease it to zero or maybe 5min. How ever it would be better if Hestia could support https://github.com/FRiCKLE/ngx_cache_purge
That is “Mod_Expires” equivalent. It may be under the log directory line but it is not an expires setting for logs. It sets the may time on cache control headers.