New server/OS update

[mouser]

i apologize for the forum downtime everyone -- i am shifting my attention to it now
there is nothing wrong with the server or data, just an overdue need to move to new operating system and/or server, and its my least favorite kind of thing so ive been dragging my feet.  i just put the forum into maintenance mode so that when the hosting company moved the database we wouldnt lose any recent posts.  But if it takes too much longer I will re-enable to forum, and we can manually move over the most recent version of the forum database after we get everything else set up.

[mouser]

It's clear the server upgrade is not proceeding at a satisfactory page, so I'm going to take the forum out of maintenance mode for now.
We will wait until we are truly ready to move over the forum before we shut it down again.

For now we are just going to stay on our current server until we get all the ducks in a row and then we can proceed to migrate in a more orderly fashion

My apologies!
-jesse

[Shades]

No worries from this end. 

As it happens, there was a pretty severe CVE (CVE-2024-6387) a day or two ago. As it was about SSH, I'm now also busy to update and migrate Linux servers in my care. And on more than one occasion, I have found that it would have taken less time to recreate a server than it does to migrate the same server to a more up-to-date version of the OS.

Most of the servers I manage are set up to for a single purpose, configuration files are backed up separately, setups are documented well and where possible, there are (version controlled) automated installation scripts. Likely that affects my opinion on the matter.

Some of those single purpose servers took almost 3 hours for an OS migration. So if your server is setup for multiple purposes, a migration or rebuild can take many more hours. Well, more than one would expect anyway.

[anandcoral]

Thanks for starting the Forum.
I was worried something happened, now no worry.

[paradisusvic]

Hello dear Jesse, I second Anand's reply:

Thanks for starting the Forum.

...also, for everything you do to keep the community up & running

It is very appreciated.

[Jedi]

Now all forum feeds (such as https://www.donationcoder.com/forum/index.php?type=rss;action=.xml ) are under Cloudflare Turnstile ... which make them unreachable by feed readers...

[anandcoral]

Now all forum feeds (such as https://www.donationcoder.com/forum/index.php?type=rss;action=.xml ) are under Cloudflare Turnstile ... which make them unreachable by feed readers...

Very Good

[KynloStephen66515]

Now all forum feeds (such as https://www.donationcoder.com/forum/index.php?type=rss;action=.xml ) are under Cloudflare Turnstile ... which make them unreachable by feed readers...

This is a temporary measure to mitigate an attack that was happening, causing the site to become completely unavailable as soon as it came back online.

[Tuxman]

Clownflare tends to be the reason for sites to be completely unavailable:
https://blog.cloudflare.com/tag/outage

But you do you, I guess.

[KynloStephen66515]

Clownflare tends to be the reason for sites to be completely unavailable:
https://blog.cloudflare.com/tag/outage

But you do you, I guess.

Only a single one of those posts has anything to do with Cloudflare being the issue.  The rest are just informative posts about widespread internet outages across the world.

[Tuxman]

Only a single one of those posts has anything to do with Cloudflare being the issue.  The rest are just informative posts about widespread internet outages across the world.

The single outage that has anything to do with Cloudflare (1):
https://blog.cloudflare.com/cloudflare-outage

The single outage that has anything to do with Cloudflare (2):
https://blog.cloudflare.com/cloudflare-outage-on-july-17-2020

The single outage that has anything to do with Cloudflare (3):
https://blog.cloudflare.com/cloudflare-outage-on-june-21-2022/

The single outage that has anything to do with Cloudflare (4):
https://blog.cloudflare.com/cloudflare-incident-on-june-20-2024

(Could be continued, but I'll leave this as an exercise to the readers.)

In all of these cases, sites without Clownflare "protection" had no problems being available everywhere in the world. These problems with their network "services" are multiplied by occasional failures of their DNS "service" (= those who use it cannot resolve domains), their CDN "service" (= those who use it, their image files are not available), their status "service" (= those who use Clownflare cannot even check why their image files are currently not available), ...

Well, after all, yes, those are very informative posts indeed. 

[KynloStephen66515]

ok so, based on those examples, that's 4 outages since 2019, totalling 246 minutes ( a little over 4 hours).

I'm by no means defending those outages, but it's a little hard not to find the following sentence a little dramatic "Clownflare tends to be the reason for sites to be completely unavailable", when it was the reason for only slightly over 4 hours, in 5 years. 

Anyway, this has absolutely nothing to with the thread.  The issue was a traffic attack, which Cloudflare mitigated within minutes of turning on Attack Mode, so regardless of your feelings on it, the service provided the desired outcome for what DC needed. /shrug

[Tuxman]

that's 4 outages

Could be continued, but I'll leave this as an exercise to the readers.