UPDATE: The Brave Browser Problem is Resolved

Thanks to Dan McGuire for the heads up. The Brave Browser problem has corrected itself.

Brave users will no longer get caught in a Cloudflare doom loop that ends with a Wordfence 404 (too many page-not-found errors for a human) block.

We’ve been working both sides of this off and on for over two months. Brave users could access our stuff, but had to do it in a private or incognito window.

No more.

We had similar issues with Edge, but those self-corrected a few weeks ago after Edge did a Browser Update. I did not see a Brave browser update come through, but I may have missed it. Despite the uproar from many, this was never a ‘Grok Side Issue.

We had numerous Brave users with no issues, and at least one who fixed it with tweaks on their end.

I can’t say why to this day, and I cannot promise it will never happen again, but Brave is Back, baby, and with it, more site traffic, which is never a bad thing.

We appreciate your patience, if you had some, and welcome everyone else back who didn’t want to be bothered with the logistics.

Author

  • Steve MacDonald

    Steve is a long-time New Hampshire resident, an award-winning blogger, and a member of the Board of Directors of The 603 Alliance and the National Heritage Center for Constitutional Studies. He is the owner of Grok Media LLC and the Managing Editor, Executive Editor, assistant editor, Editor, content curator, and more (yes, there's more) at GraniteGrok.com. Steve is also a former board member of the Republican Liberty Caucus of New Hampshire, the Republican Volunteer Coalition, and has worked for or with many state and local campaigns and grassroots groups, and is a past contributor to the Franklin Center for Public Policy.

    View all posts
Share to...