wolstech

OK... Please check your PMs for details on what I did for you, however I've gotten your website up and running for you http://mail2ftp.heliohost.org Do you want your forum accounts combined? You now have mailftp, mail2ftp, and Lena. Lena is your original and the one associated with the fixed account.

All of the backups are doing that for some reason... Also, your accounts are a bit of a mess because it seems like your account is on all 3 servers at the moment...archived on Johnny, a new one on Ricky that doesn't work (shows inactive page for Johnny???), and apparently one on Tommy as well that was unaccounted for in the system (I tried just moving your archive for you since you're our longest-term customer and just have a static HTML site...it blew up due to the existing Tommy account and a domain conflict with the Ricky account you made). Let me get this mess cleaned up for you...

This account has a compromised CMS installation that has been affected by the recent AnonymousFox hack and cannot be unsuspended. An invitation will be sent to you shortly so you can create a new account. Please restore your data using a backup. The data from your old account cannot be recovered or returned to you due to the possibility of the account having been used for Phishing. As a reminder, when selecting a CMS, we highly recommend that users not use WordPress. WP and it's extensions are notorious for having security issues such as the one you (and everyone else on Tommy) experienced, and it has the worst security track record of any CMS out there. Using a different program will help prevent this from happening again.

Johnny accounts are intentionally disabled due to scheduled maintenance. https://www.helionet.org/index/topic/33812-johnny-maintenance/

Johnny accounts are intentionally disabled due to scheduled maintenance. https://www.helionet.org/index/topic/33812-johnny-maintenance/

It's a botnet, so impossible to identify the source. The actual attack looks like it's coming from all over the world since botnets are usually made up of random PCs that have malware.

This account has a compromised CMS installation that has been affected by the recent AnonymousFox hack and cannot be unsuspended. An invitation will be sent to you shortly so you can create a new account. Please restore your data using a backup. The data from your old account cannot be recovered or returned to you due to the possibility of the account having been used for Phishing. As a reminder, when selecting a CMS, we highly recommend that users not use WordPress. WP and it's extensions are notorious for having security issues such as the one you (and everyone else on Tommy) experienced, and it has the worst security track record of any CMS out there. Using a different program will help prevent this from happening again.

Sort of. They use a botnet (hence the first D, "distributed", in DDoS), so the connections come from random IPs making a conventional firewall useless. We do already restrict too many connections from an IP during these attacks, which helps, but they just bring more/different bots instead. The firewall uses quite a bit of resources to detect and refuse these connections too. A hardware firewall appliance would be more efficient here. The actual attack method varies. One method (was used on Johnny) entails wasting server resources by opening a ton of connections and just leaving them open all day without closing them. This causes the server to leave Apache processes open waiting for the content of their request that never comes. The connections do eventually time out, but the attacker just reopens the connections when that happens. This means decreasing the max connection time actually increases load (process for timed out connection closing, and new process for replacement connection starting), making it useless as a mitigation. The second is request flooding. In that method, they just send requests for a targeted website over and over again as fast as possible, which results in the server using its resources to fulfill these requests over and over again, leaving it little time for legitimate requests to be processed. Consider that a typical request involves: Apache receiving the request and finding the file, then launching PHP. PHP then runs the script in the file, which often asks MySQL for data. PHP then sits there in memory waiting for that data, then when it gets it, uses that data, finishes its script and returns a webpage to Apache to send out. Doesn't seem to bad when you're handling a few hundred at a time, but when you want to suddenly do 1 million of them concurrently, it becomes an issue...the server gets backlogged, and/or runs out of memory and crashes. This also often manifest as invalid requests or junk packets with no or useless data being sent...these aim to clog up the network as opposed to waste the CPU's time. This is what I believe was happening on Tommy. The result is the same: legitimate requests cannot get through and the websites on the server get slow or go down.

Done. You should now be able to log in and your website should be working again.

All Johnny accounts are intentionally disabled due to maintenance. Please see https://www.helionet.org/index/topic/33812-johnny-maintenance/

Your account was archived because you haven't logged in for quite a while. We have a limited amount of space on our servers, and occasionally we have to remove the unused accounts to make space for new users. To prevent your account from becoming archived again please remember to log in at https://www.heliohost.org/login/ at least once every 30 days. Unarchiving...

The account calbet has been merged with zavyerr, and the email address has been updated.

The other username is already taken by what appears to be an older account of yours (it's from December 2016 and has the same profile picture). If that's yours, please post from that account to confirm you own it and I'll merge everything together into one.

Invite sent.

Invite sent.

You have to unpack the backup and manually restore everything anyway. You can't upload the backup and have the server automatically restore it. The major change will be your database users and database names, because the main account's username is different.

They don't care about us They just get upset because they aren't allowed to phish here.

It counted. The 2FA is just incompatible with our login tracking system. Not sure whether Krydos can fix that or not...

There is no local network. All of our equipment faces the internet directly, a lot of things just so happen to have consecutive IPs because we bought the IPs as a group. Every single IP we have is publicly routable.

Have you tried this? I need to know if this works or not. If it does, 2FA is to blame. If it does not, our website is just broken.

That account cannot be unsuspended because it was involved in a hacking attempt. Normally I'd send you an invite, but we can't create new accounts right now because of this issue: https://www.helionet.org/index/topic/33857-home1-unavailable-on-tommy/ Once that's fixed, I can send you an invite for a new account.

It's caused by this: https://www.helionet.org/index/topic/33857-home1-unavailable-on-tommy/ When that issue gets fixed, this will be too. Everyone with an account created after mid-April is likely seeing this, which is basically everyone who had to deal with AnonymousFox, and all the new users since that time.

You weren't blocked when you made your request so I couldn't unblock you.

@sagnik: Nope. The /home1 volume (which contains his home folder) isn't mounted for some reason. He wouldn't even be able to get to an htaccess file because as far as the server is concerned, his home folder is missing. Most users with an account created on or after April 19th 2018 probably have an account with their home folder on /home1...the /home1 was the added space from our NAS purchase. It probably dropped offline due to the DDoS traffic or the null routing yesterday and just needs to be remounted. The bad news is I don't know how to do that, which is why we're waiting for Krydos...

It counted that time. Try logging in using the https://heliohost.org/login/ page now, leaving 2FA disabled. If it works, the 2FA is incompatible with our system.