Cloudflare notice

[Sparko]

If you have seen a Cloudflare notice showing up when you first come on the site, it is because we have turned on our Distributed Denial Of Service attack protection. DDOS's are caused when a group of computers are infected with a virus and form a "botnet" that troublemakers can use to flood a website with so many page requests that it slows down to a crawl or hangs. Most members of these botnets are not even aware they have been compromised. This is a good reason to keep your antivirus and malware protection up to date.

Cloudflare is a service that prevents these attacks from getting through by vetting the source of the page request before letting it through. Similar to a firewall. If you are a normal user, you will just see a "wait" message for a few seconds when you first access the site . After than your access should be normal. If you were a botnet, you would be blocked. The message may pop up again if you switch tabs again or post.

[Ronson]

If you have seen a Cloudflare notice showing up when you first come on the site, it is because we have turned on our Distributed Denial Of Service attack protection. DDOS's are caused when a group of computers are infected with a virus and form a "botnet" that troublemakers can use to flood a website with so many page requests that it slows down to a crawl or hangs. Most members of these botnets are not even aware they have been compromised. This is a good reason to keep your antivirus and malware protection up to date.

Cloudflare is a service that prevents these attacks from getting through by vetting the source of the page request before letting it through. Similar to a firewall. If you are a normal user, you will just see a "wait" message for a few seconds when you first access the site . After than your access should be normal. If you were a botnet, you would be blocked. The message may pop up again if you switch tabs again or post.

When I initially link to TWEB it goes through https. After a screen or two, it changes to http and I get the cloudfare notice. Should I have concerns about that? My home browser is set up to avoid http sites.

[Sparko]

When I initially link to TWEB it goes through https. After a screen or two, it changes to http and I get the cloudfare notice. Should I have concerns about that? My home browser is set up to avoid http sites.

Tweb is HTTP. The software we are running can't do HTTPS.

[Ronson]

https://www.theologyweb.com/campus/s...udflare-notice

This above is currently the page I am posting from, using Explorer.

[NorrinRadd]

If you have seen a Cloudflare notice showing up when you first come on the site, it is because we have turned on our Distributed Denial Of Service attack protection. DDOS's are caused when a group of computers are infected with a virus and form a "botnet" that troublemakers can use to flood a website with so many page requests that it slows down to a crawl or hangs. Most members of these botnets are not even aware they have been compromised. This is a good reason to keep your antivirus and malware protection up to date.

Cloudflare is a service that prevents these attacks from getting through by vetting the source of the page request before letting it through. Similar to a firewall. If you are a normal user, you will just see a "wait" message for a few seconds when you first access the site . After than your access should be normal. If you were a botnet, you would be blocked. The message may pop up again if you switch tabs again or post.

I keep my AV protection up to date. Even so, until Admin lowered the Cloudfare setting to "Medium," I was totally unable to access the site, even after performing the Captcha ritual.

[NorrinRadd]

Even with the "medium" setting presumably still in place, I was totally blocked for several hours tonight. Even the Captcha ceremony did not admit me.

I have run two separate scanners over a period of nearly two hours, and no problems were found on my system. If my being blocked is because Cloudfare believes I'm part of a botnet, it is one my scanners can't detect.

[mikewhitney]

This article seems half related to the tweb issue

[Sparko]

This article seems half related to the tweb issue

We were having the problems before we even turned on the cloudflare service. We had it paused completely when we were having all of the slow down. I turned it on and saw how much traffic our site was getting so I turned on attack mode.

We are still receiving way too much traffic which indicates an attack, since we don't have that many users. last check was showing over 9,000 page requests hitting us. I blocked some IP addresses that seemed to be causing much of it. Not sure if that was a web crawler or a botnet. I turned off attack mode and switched to "high" mode for now. I also rebooted tweb to clear out some memory problems.

If the traffic drops after this I will pause cloudflare again.

[mikewhitney]

We were having the problems before we even turned on the cloudflare service. We had it paused completely when we were having all of the slow down. I turned it on and saw how much traffic our site was getting so I turned on attack mode.

We are still receiving way too much traffic which indicates an attack, since we don't have that many users. last check was showing over 9,000 page requests hitting us. I blocked some IP addresses that seemed to be causing much of it. Not sure if that was a web crawler or a botnet. I turned off attack mode and switched to "high" mode for now. I also rebooted tweb to clear out some memory problems.

If the traffic drops after this I will pause cloudflare again.

The article was initially dated to July 17. It was mostly the mention of Cloudflare that got my notice even though the problem the article described was apparently about broader connectivity issues.