Tim

Actually, found a bunch more starting with wp-to-buffer-pro and assume they all go together.

Connection Timeout: 1s
Read Timeout: 1s

Thank you for the fast response. The update did seem to fix the problem.

Thank you.

The same issue… receive an “Unauthorized” message in a red bar when purging individual pages.

Here: https://www.mychesco.com/

It is a news blog and a new article is posted hourly (sometimes more)… standard posts.

As I have been monitoring this, it is hit or miss with purging the front page. Sometimes it works, sometimes not.

I have been with DreamPress and used the plugin for years. The only recent change is the WordPress update.

I wanted to again give this topic a bump as this issue occurred again. I have disabled wp-emoji-release.min in an attempt to protect visitors when it occurs. Did anyone discover why this is happening?

I will reach out to DreamHost’s support today. Thank you.

Is there a snippet that I can add to my functions.php to schedule a full site purge?

It was 5 seconds old because I cleaned varnish using the plugin, as I mentioned, to check the header after turning off Cloudflare.

So, is your advice to contact DreamHost’s support?

I temporarily turned Cloudflare off, then purged Varnish…

Response Headers for https://www.mychesco.com/?call_custom_simple_rss=1&csrp_cat=-17434&csrp_thumbnail_size=735%C3%97400

accept-ranges: bytes
age: 5
cache-control: must-revalidate, public, max-age=300, stale-while-revalidate=360, stale-if-error=43200
cf-edge-cache: cache,platform=wordpress
content-encoding: gzip
content-length: 9368
content-type: text/xml; charset=utf-8
date: Fri, 08 Apr 2022 19:37:57 GMT
expires: Sun, 08 May 2022 19:37:49 GMT
server: Apache
strict-transport-security: max-age=31536000
vary: Accept-Encoding
via: 1.1 varnish (Varnish/6.5)
x-cache: HIT
x-cacheable: YES
x-powered-by: DreamPress
x-varnish: 26476987 28574484

Still cacheable.

I had already tried the curl -X PURGE "https://123.45.67.89/" -H "host:www.example.com"… of course, with my IP address. It did not work either.

I’m not at all sure how Cloudflare is part of the issue here. If I do a full site purge of Vanish, without touching Cloudflare, the Ugly URLs (both created by the site search and Custom Simple Rss plugin) do clear and update… again showing that Cloudflare is being bypassed.

…you can’t actually use the domain like that? …if the domain added is the same as the domain the site is on? I’m not really sure that I understand what you mean.

Regardless, this seems to have exposed another issue… search results (example: https://www.mychesco.com/?s=coatesville).

Response Headers:

age: 45
alt-svc: h3=":443"; ma=86400, h3-29=":443"; ma=86400
cache-control: must-revalidate, public, max-age=300, stale-while-revalidate=360, stale-if-error=43200
cf-apo-via: origin,qs
cf-cache-status: BYPASS
cf-edge-cache: cache,platform=wordpress
cf-ray: 6f8ceae24ffe1a0f-EWR
content-encoding: br
content-type: text/html; charset=UTF-8
date: Fri, 08 Apr 2022 18:03:03 GMT
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Fri, 08 Apr 2022 19:02:15 GMT
link: <https://www.mychesco.com/wp-json/>; rel="https://api.w.org/"
nel: {"success_fraction":0,"report_to":"cf-nel","max_age":604800}
report-to: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=tWfLiJnmFR0TMjd%2F4TKlk8dAAnoboHpIVxSs5%2FHbUN6NOtLpqys9xSa8zyM9W3S6Z3WbsrA9e39B7G4PGPpdcGWGqSSt8GCG9K5JPBt8OnYolK94xJRjHl0ozXsM5PQ%2FFeOmqtAUINWvtSKsiSw%3D"}],"group":"cf-nel","max_age":604800}
server: cloudflare
strict-transport-security: max-age=31536000
vary: Accept-Encoding
via: 1.1 varnish (Varnish/6.5)
x-cache: HIT
x-cacheable: YES:Forced
x-powered-by: DreamPress
x-varnish: 31268004 27626825

So, it looks like Varnish is caching search results which will stick around essentially until I do a full site purge. That’s not right, is it?

I am using cloudflare but that page is setup to bypass cloudflare’s cache… which is confirmed in the header.