Varnish Port (Cloudways)

Hi,
as far as I know, Cloudways uses 8080 for the varnish. You can double-check with Cloudways in this regard.

Chiming in here … I remember Cloudways support told me their services (including Varnish) run on port 8080, however, I can see the same issue.

E.g. If I change widgets in WordPress I need to go to Cloudways to purge the Varnish cache manually from there.

Would love to learn more how to troubleshoot / solve this.

Is there a reason why there is an additional setting only for Cloudways Varnish?

Hi,
Have you guys enabled the Cloudways Varnish option? And according to you the process does not work even after that?

Is there a reason why there is an additional setting only for Cloudways Varnish?

– Yes cause the Cloudways handle the URL paths in a bit different way than normal varnish.

If I change widgets in WordPress I need to go to Cloudways to purge the Varnish cache manually from there.

– The system will only auto-purge if you post or update any pages or posts or CPTs. But if you are making any changes in the Widget or Menues or some plugin settings etc. you have to manually Select Purge Whole Cache from the top admin bar or from Plugin settings page. That should purge your Cloudflare cache as well as Cloudways Varnish Cache.

Thanks Saumya for getting back to me. I can’t talk for the original poster but it’s not fully clear to me if Varnish gets actually purged.

– The system will only auto-purge if you post or update any pages or posts or CPTs. But if you are making any changes in the Widget or Menues or some plugin settings etc. you have to manually Select Purge Whole Cache from the top admin bar or from Plugin settings page. That should purge your Cloudflare cache as well as Cloudways Varnish Cache.

Exactly. However, I am not sure if the manually purging the entire cache works. The setting to include Varnish is enabled. Even if I manually click on Purge Varnish Cache I am not sure if it actually works.

I wonder if there is a reliable method to test if Varnish got purged or not.

Scenario 1:
1. Added new widget
2. Manually purged whole cache including varnish
3. Widget not visible
4. Go to Cloudways and purge cache there
5. Widget visible

Later I tried the exact same thing again the other way round but the result was different
1. Deleted new widget
2. Manually purged whole cache including varnish → no difference
4. Manually purged fallback cache, varnish cache → no difference
5. Widget still visible even though I deleted
6. Check URL with /?nocache → shows the expected result
7. Cleared Redis Cache → no difference
8. Deleted Redis → no difference
9. Restarted Memcache → no difference
10. Restarted Redis → now that worked

I tested many different scenarios. It’s just not fully clear yet as the outcome is not obvious to me.

Do you know if I can reliably test if Varnish got really purged via Cloudflare Super Cache “purge whole cache”?

Can you do something with the hint that /?nocache does work from the very beginning? With several cache levels (browser cache, fallback, cloudflare, varnish, redis, memcache) I am not sure what /?nocache actually means

Thanks so much!

Markus

Huh! That is wired. Have you double confirmed the port number from Cloudways if it is still on 8080?

I double confirmed now with Cloudways that the port is still 8080. Also they told me that Varnish will be auto purged every 4 hours.

I did not test with changes in Posts/Pages, but changes on widgets definitely required some additional purging & clearing.

I’ll let you know if I figure out more when testing. If you have any idea please also let me know.

Thanks

OK. Let me know when you test further. But honestly, I have no idea what is happening here.

I just had the same situation again on a different website (and different Cloudways account).

Something was off after updating plugins. I cleared / purged all cache.
It did not help. Cache did not get purged.

I needed to go to Cloudways Platform to manually purge Varnish cache.
I could notice immediately the difference. Cache got purged.

I have no explanation for it. Only that it obviously does not work.

I am just not sure if Cloudways could do something about it. Or if there is something to do on the plugin to make it work.

Hey @markussss,
Can you let me know your domain name?

I learned it the hard way already to add sensitive information here, as I am not allowed to delete it afterwards. Can I somehow send this private to you?

You can share your site URL via https://safenote.co/

That’s a good idea… it happened on both of those sites I mentioned. I do have other sites as well with Cloudflare, Cloudways, and your plugin

https://safenote.co/r/61928f2ae02163@24867953

I figured something out that might help.

Clear all cache when using Cloudways + Cloudflare + Cloudflare WP Super Plugin
1) Manually purge Cache in Cloudways Platform (platform.cloudways.com)
2) Purge whole cache from Cloudflare WP Super Plugin
→ then really all cache is cleared.

e.g. I change a product from in stock to out of stock and it shows correct.

What does not work?
– Only Purge whole cache from the plugin (even though its set up correctly with Varnish Cloudways setting and port 8080)
– Manually purge Cloudways varnish via plugin and then again purge whole cache
– Only purge varnish cache from Cloudways platform

It requires the combination of purging varnish at the CW platform and only after that purge whole cache from your plugin.

I hope that makes sense to you and you can do something with this information.

cheers
Markus

Hi @markussss,
So, you are saying that if you purge the varnish cache from the plugin settings page then it is getting cleared but automatically it is not getting cleared?

Also, can you try setting the log verbosity in the plugin settings to HIGH and then see during the varnish purging if you are getting any error or messages?

So, you are saying that if you purge the varnish cache from the plugin settings page then it is getting cleared but automatically it is not getting cleared?

No, varnish cache does not get cleared at all with the plugin. I must manually purge varnish at the Cloudways Platform itself AND additionally also purge all cache with the plugin.

Also it must be done in this order.

Attached the log file – I only added the part when I clicked ‘purge varnished cache’
https://www.dropbox.com/s/ss5a7b61euamzxz/varnish-log.txt?dl=0