Chandra Patel

Hello,

This has been fixed automatically. Jetpack connection was the same and just updated domain, so transfer was not needed. I also able to connect another site with Jetpack as new connection.

So, closing this topic.

Thanks,
Chandra

Hi @alexclassroom

Sorry for the late reply. We have fixed this issue and released the v2.2.2.

Please update the plugin and let me know if you still facing the issue.

I’m marking this ticket as resolved.

Thanks,
Chandra

Hello @leondari

Thanks for the confirmation. If you are happy with our plugin now, would it be possible to change your rating?

Thanks,

Hello @leondari

My apologies for the inconvenience. We have fixed the timeout issue with FastCGI cache and released plugin version 2.2.1

Please update the plugin and let me know if it fixes the issue at your end.

Thanks,

Hello @leonardorodriguez

We have fixed the timeout issue with FastCGI cache and released plugin version 2.2.1

Please update plugin and let me know if it fix the issue at your end.

Thanks,

Hello

My apologies for the inconvenience. We are looking into this issue.

Can you please share what the Caching Method and Purge Method(in case of FastCGI) have been set in plugin settings? Can you please share more details like other plugin settings, error messages in the log file, and any other custom settings like defining “RT_WP_NGINX_HELPER_CACHE_PATH” constant in case of FastCGI.

So it will help us in debugging the issue.

Thanks,

Hello,

Thanks for the reporting issue and submitting PR. I’ve merged PR.

Hello Jeff Cleverley,

We’ve released plugin version 2.0.2 and in this version, this issue has been fixed. Please update the plugin.

Thanks,

if there are two networks running on the same server, will a network admin purge on one network then also purge the entire cache of the other network?

Yes, It will purge the entire cache of the other network.

Hello RavanH,

I apologize for the delay in reply.

It’s getting more and more annoying to have to explain to site admins that the clear cache does not work and they need to way for the cache to expire on its own…

We’ve tested with possible use cases, but purging from site/network admin working fine.

I’ve set a different one on Settings > Nginx Helper, matching the prefix used by Redis plugin (as set in wp-config by the WP_CACHE_KEY_SALT constant).

WP_CACHE_KEY_SALT constant used by Redis plugin for object cache and it’s not used by Nginx Helper for page cache.

So, the Nginx Helper prefix setting MUST be “nginx-cache:” as long as no nginx file is changed manually?

Yup. If prefix changed in nginx config file then need to change in Nginx Helper prefix setting as well.

I thought it had to match the Redis plugin prefix.

No, Redis/Nginx Helper plugin prefix is different.

So this means all sites/networks on the same server will get all their caches cleared when one site/network does a “purge all”?

Site Admin: Admin bar Purge Cache will purge the page cache of that site.
Network Admin: Admin bar Purge Cache will purge the page cache of all the sites.

Remains the Purge Cache menu not working on the front end admin bar. This is caused be the fact that the purge_all method is only hooked to admin_init so does not check any purge action on the front end.

Yup. But instead of removing “Purge Cache” from front-end admin bar, we’ve made changes and now it will purge the current page cache. Also, we’ve rename button to “Purge Current Page” in the front-end admin bar. PR have been merged but the plugin is not released yet with this change. Please let me know your suggestion on this.

Is site/network admin “Purge Cache” working fine after changing prefix in nginx helper plugin?

Thanks,

• This reply was modified 6 years ago by Chandra Patel.
• This reply was modified 6 years ago by Chandra Patel.

Hello RavanH,

I apologies for the delay.

We’ve tested following use cases with latest version of Nginx Helper plugin and EasyEngine V4 & V3.8.1.

REGULAR NETWORK

1. Admin bar Purge Cache, front end: nothing (expecting page cache only)
– Yes, this is not working. We are working on to resolve this.
2. Admin bar Purge Cache, site admin: nothing (expecting site cache)
– We’re unable to replicate this issue.
3. Admin bar Purge Cache, network admin: clears entire cache (expecting site cache only)
– Yes, it will purge entire page cache. Needs to change Admin bar menu name to “Purge Entire Cache” for network admin.
– (expecting site cache only) – Can you please give more details on this use case?

MULTI-NETWORK – PRIMARY NETWORK

1. Admin bar Purge Cache, front end: nothing (expecting page cache only)
– Yes, this is not working. We are working on to resolve this.
2. Admin bar Purge Cache, site admin: nothing (expecting site cache)
– We’re unable to replicate this issue.
3. Admin bar Purge Cache, network admin: nothing (expecting site cache only)
– Yes, it will purge entire page cache. Needs to change Admin bar menu name to “Purge Entire Cache” for network admin.
– (expecting site cache only) – Can you please give more details on this use case?
4. Purge Entire Cache button on the Nginx Helper super admin page: nothing (expecting entire cache)
– We’re unable to replicate this issue.

Can you please provide the logs of Redis and Nginx Helper plugin for above use cases to debug the issue further?
– You can get Nginx Helper plugin log file path from plugin settings page.
– For Redis log, Please follow this URL. https://stackoverflow.com/questions/16337107/how-to-access-redis-log-file/16340289#16340289

Also, can you please check in Nginx Helper log whether page cache key which Nginx Helper plugin trying to purge is same as in Redis server?

Thanks,

Nginx Helper plugin doesn’t save any kind of user information. This plugin has only back-end functionality to purge the cache.

Thank you HansRuedi Keller for your positive review and checking this plugin.