Nginx cache purge wordpress plugin

jlguerrero · December 10, 2020, 7:23pm

I follow the plugin’s instructions and I get this error:

In /etc/nginx/nginx.conf I find the cache path to be: /var/cache/nginx

But I think there must be a local part for the web cache. I suppose there will be permissions issues.

I also tried: /home/myuser/.cache

Any ideas?

eris · December 10, 2020, 8:06pm

For fastcgi there is currently no cache set.

For proxy cache the current path is /var/cache/nginx/ how ever this due a bug in the template

This pull requests should fix the issues how ever the path is then /var/cache/nginx/domain.com/ for proxy and
/var/cache/nginx/fastcgi/domain.com/ for fastcgi

But you will still run with the permission issue as php runs as the user and nginx as www-data

jlguerrero · December 10, 2020, 9:12pm

Thank you very much @eris.

I don’t know how to apply the fix.

I tried this though:
Plugin: /var/cache/nginx/domain.com/
SSH:
cd /var/cache/nginx/
chown www-data:user -R domain.com

No results

eris · December 10, 2020, 9:31pm

If you are using “proxy” cache (Apache2 + Nginx) replace in the caching.(s)tpl

github.com

hestiacp/hestiacp/blob/22cab5d6a88935ffefb1c3847dc35d5ea29597e3/install/deb/templates/web/nginx/caching.stpl#L20


ssl_certificate_key  %ssl_key%;
ssl_stapling on;
ssl_stapling_verify on;
error_log  /var/log/%web_system%/domains/%domain%.error.log error;
include %home%/%user%/conf/web/%domain%/nginx.hsts.conf*;
location / {
    proxy_pass      https://%ip%:%web_ssl_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           %sdocroot%;
        access_log     /var/log/%web_system%/domains/%domain%.log combined;

In the .tpl it the same key value but a few lines higher…

I don’t know if we can set the default permissions via nginx, So we change it to 660 instead of 600 and give it permission so we can remove it.

Currently I just use a limited cache length of 5 minutes this will save the biggest buttload traffic is then handled by that.

And second option would be integrating https://github.com/FRiCKLE/ngx_cache_purge into Nginx how ever this would require an custom template and custom Nginx.

emrahk · June 16, 2021, 7:30pm

I really hope this feature comes in future versions.

Raphael · June 16, 2021, 8:14pm

We will not build a custom nginx version for hestia, so this feature will probaly never arrive .

jlguerrero · June 16, 2021, 9:37pm

Maybe if you dropped debian?

Raphael · June 17, 2021, 4:15am

Also for debian it would be 2 or 3 versions, so it does not matter. We will NOT ship a custom nginx version, it is just to much work for build and testing - this has been discussed again a few weeks ago within the team.

jlguerrero · June 17, 2021, 7:00am

I understand the message. I was only saying that if you stopped supporting Debian you might have more time (and I use Debian myself) with the hope that in time you will start considering the idea. It is my long term strategy… Just drop the idea and then wait until you completely change your minds and devote your lives to develop for free.

Raphael · June 17, 2021, 7:16am

The mind in that case will not be changed, because providing a own custom nginx version will cost multiple thousand us dollars monthly, calclulated in needed time for compilation, support and testing. The only way would be to have someone who takes over the expenses (3000-4000 usd monthly) - until then and also for the future, this is a clear “no”. Also dropping debian isnt an option.

Ubi · June 17, 2021, 7:20am

Finally i read something that has a sense. Amazing “non-sense” discussions here lately.

eris · June 17, 2021, 7:41am

That last thing all ready happened…

This issue is not the creating part but the “period” after keep it maintained and regularly updated and tested.