it seems to be happening more and more lately.

Sent from my SM-S928U using Tapatalk

(11-04-2024 11:27 PM)hburg Wrote:  it seems to be happening more and more lately.

Sent from my SM-S928U using Tapatalk

I've noticed that as well. I couldn't log in on my phone for most of the day. Something about SQL Error 1114.

it has happened several times this week with sql errors. It's becoming a problamatic issue.

(11-06-2024 06:06 PM)andybible1995 Wrote:  

(11-04-2024 11:27 PM)hburg Wrote:  it seems to be happening more and more lately.

Sent from my SM-S928U using Tapatalk

I've noticed that as well. I couldn't log in on my phone for most of the day. Something about SQL Error 1114.

Same. Mobile and desktop.

Big surges in bot traffic.

Just now: 8,663 users active in the past 30 minutes (171 members, 35 of whom are invisible, and 8,490 guests).

At least 2/3 of that guest number is a bot surge.

Excellent. Turning off guest read access is driving them away quite fast.

7,882 users active in the past 30 minutes (173 members, 24 of whom are invisible, and 7,708 guests).

For a few weeks I have only been able to log in on my laptop (HP) and not my iphone or ipad. I'm getting an error that says 400 Bad Request. Request header or cookie too large. nginx.

Both are up to date with IOS and I have cleared cookies and cache. Anyone else seeing this? Thanks. I also have seen what has been described here.

(11-07-2024 07:44 AM)Section4 Wrote:  For a few weeks I have only been able to log in on my laptop (HP) and not my iphone or ipad. I'm getting an error that says 400 Bad Request. Request header or cookie too large. nginx.

Both are up to date with IOS and I have cleared cookies and cache. Anyone else seeing this? Thanks. I also have seen what has been described here.

Your session cookie is likely broken/corrupted.

Clear your browser's cache and cookies for CSNbbs.com, then exit the browser. Open it back up and come back here and login. You should be fine then.

I'm upgrading from banning subnet ranges to banning entire AS blocks.

https://www.ip2location.com/as212238

(11-06-2024 11:03 PM)georgia_tech_swagger Wrote:  Excellent. Turning off guest read access is driving them away quite fast.

7,882 users active in the past 30 minutes (173 members, 24 of whom are invisible, and 7,708 guests).

Chipping away with bans. All of OVH. All of Hetzner. Some RU residential ISPs.

7,211 users active in the past 30 minutes (353 members, 59 of whom are invisible, and 6,856 guests).

These guys are a big part of the problem

https://www.ip2location.com/as4771
https://www.ip2location.com/as9790

Did another huge ban wave on Ireland and New Zealand. Let's see how much this drops in 30m.


6,722 users active in the past 30 minutes (310 members, 60 of whom are invisible, and 6,411 guests).

5,248 users active in the past 30 minutes (311 members, 49 of whom are invisible, and 4,934 guests).

Excellent.

4,737 users active in the past 30 minutes (327 members, 55 of whom are invisible, and 4,408 guests).

4,478 users active in the past 30 minutes (322 members, 60 of whom are invisible, and 4,154 guests).

Nuked more NZ and AU ranges.

3,983 users active in the past 30 minutes (260 members, 48 of whom are invisible, and 3,721 guests).

That may be about as low as I can go and I blocked really aggressively outside the US. I may wave the white flag and put a Cloudflare WAF in front of the site.

Sweet sweet relief

2,744 users active in the past 30 minutes (236 members, 42 of whom are invisible, and 2,506 guests).

Still dropping

(11-07-2024 07:57 AM)georgia_tech_swagger Wrote:  

(11-07-2024 07:44 AM)Section4 Wrote:  For a few weeks I have only been able to log in on my laptop (HP) and not my iphone or ipad. I'm getting an error that says 400 Bad Request. Request header or cookie too large. nginx.

Both are up to date with IOS and I have cleared cookies and cache. Anyone else seeing this? Thanks. I also have seen what has been described here.

Your session cookie is likely broken/corrupted.

Clear your browser's cache and cookies for CSNbbs.com, then exit the browser. Open it back up and come back here and login. You should be fine then.

Thanks for the tip. It worked!