I turned off UAM (Under Attack Mode) for a bit and I am monitoring.

Update: it’s back on

Update: UAM is on but allowing the “good bots” to bypass. So far so good.

Bit by bit, I will restore the site to some normalcy.

I added a forum plugin and a new rule to bypass the CloudFlare check.

So after you login or if you do anything while logged in, you will get a cookie. This cookie allows you to bypass that check. If you log out, the cookie remains. As long as you visit once a year, you should never see that check again — until I’m testing something else. ;-)

@crockett36 Thanks I appreciate it. It feels like I’m playing a war game with these stupid bots.

Me: turn off Singapore, China, and Brazil
Bots: hmmm
Me: Phew it looks like it’s getting bett…
Bots: Launch Agentina, Vietnam, Mexico, Chile, Japan, …
Me: <censored>

@LaFayette I opened a PR to add the Triplea-Version header to requests to this site.

https://github.com/triplea-game/triplea/pull/14308

I prefer these headers over what I’m currently doing, which the bots might figure out eventually.

Temporarily turning it off for 5 minutes to test a TripleA build.

Update: test completed and passed.

We are back in business.

@Panther What version of TripleA? Probably 2.6++ right?

@msoot @VictoryFirst is it working again?

“Under Attack Mode” for the bot filtering also causes problems with TripleA.

However, I just created a new rule that will allow TripleA versions 2.6 and later to work properly on the site. I did a smoke test and I think it should work. Please try it.

@VictoryFirst It’s because of the bot attacks on the site. The AI crawlers are effectively DDOSing the site taking it down. However the thing that prevents this also prevents TripleA from working.