Are you getting an error when loading tidbits.com?

A few readers are reporting that they see a white screen with the error “Please wait while your request is verified error” when they try to load tidbits.com. The problem seems to vary between browsers and platforms, so many people who see it in one browser or platform don’t see it on another.

The error is coming from the Immunify360 firewall at Cloudways, the host we switched to fairly recently, and I believe it started no earlier than October 25. Cloudways support thought it was related to a Browser Cache TTL setting at Cloudflare, the content delivery network we use, but the problem has persisted for some even after setting that to Respect Existing Headers.

The other oddity is that one person saw the problem with www.tidbits.com but not with tidbits.com. I’m still trying to understand how a CNAME could behave differently from A record in this regard.

Anyway, no need to reply if everything is working for you, but if you’re seeing the problem, I’d like to add you to my data points. Thanks!

I’m seeing it @ www.tidbits.com, but tidbits.com is OK. This is on Monterey 12.7.6 (21H1320) and Safari Version 17.6 (17618.3.11.11.7, 17618)

It’s still trying www…

1 Like

Thanks! That’s good confirmation that something is borked when people go through the www CNAME.

And now I can reproduce in Safari on macOS 15.1. Finally, I can see it happening!

It’s some sort of weird redirect that just keeps trying to load over and over again.

Arc 2024-10-31 at 10.08.38

Seeing the same issue on M1 Air using Sequoia with Firefox and also on my old Catalina Mac Mini but only with www.tidbits.com.

1 Like

Seeing problem with www.tidbits.com using Firefox and Chrome on Windows 11.

1 Like

Just keeps banging on it. Never does work.

Also Firefox 130.0.1

1 Like

Try it now. I just purged the Cloudflare cache on the theory that perhaps something was stuck in there even though I’d reset the necessary options. www.tidbits.com seems to be working for me now.

1 Like

Yes, working now!

1 Like

As you probably know, an HTTP request includes the full URL, including the hostname. This is how virtual hosting (where lots of domains share a single server and its IP address) works.

So it is quite possible that the web server/CDN responding to the request is handling the two URLs differently, even if the DNS records point both at the same IP address.

Works now. When I get home I’ll see if it also fixes the broken image at the top of TidBITS emails.

1 Like

The image https://marketing-image-production.s3.amazonaws.com/uploads/7c03f61854ccf49ce5845d1562c8063b52940f9d28fc4b5b7a304a6425886fe94ae00c0422e11a888683fb45cf512c459027aa741f0ae57f9ef2cd78ce5cde8f.png at the top of TidBITS emails is no longer broken.

Well, that’s great since troubleshooting that would have exploded my head.

It turns out that Cloudways just installed a firewall on October 25 without saying anything, which is what caused all this. I had to make several downstream configuration changes to get it all working, but it took quite some time to figure out what was wrong and find all the settings.

Cloudways seems to do a decent job of just serving the site, but I can’t recommend them based on their haphazard way of changing the environment with no notice.