wolstech

Try using your account username (lafl) instead of your email address to log in.

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...

The heliohost.org side of things should update itself eventually, but it can take several hours to do so. I manually updated it for you. I've manually updated your forum account to match as well.

Is it the same update failing repeatedly, or is it catching up on installing updates? The update settings have an option for update history that will tell you what it's been up to. As for receiving tons of updates...that's pretty normal for Windows 10 unfortunately. If you have Pro, you can use gpedit to turn off the automatic updates (or at least remove the restart nags so it only does them when you decide to shut down). If you have Home, your only choice is to completely kill WU by disabling it's service.

Tommy is currently unable to accept password resets because cPanel is down due to /var being full.

/var is indeed full again...http://heliohost.grd.net.pl/disk-space/

It got cancelled because it kept overheating during testing based on what I’ve read. They couldn’t fix the issue with keeping it cool. Their devices still support other wireless chargers though...

Unblocked. The only way to avoid this is to not use basic auth here. Our system is very sensitive to this sort of thing and will block any user who logs in incorrectly after a few attempts (we've had run-ins with brute-force bots trying to break into user websites as well as non-public stuff before).

Unblocked. For that sort of login, you can't. Failing to log into a basic auth implementation (e.g. clicking OK several times to get rid of the window) will get you blocked after a few tries. If you cancel it, it should die instantly with a 401 or 403 error. I recommend avoiding using such logins if you can because it means it's very possible for your users to get themselves blocked from your website.

Done. You should now be able to log in and your website should start working within 2 hours.

Unarchiving...

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

Unarchiving...

The best way to keep people from breaking into WP is to not use WP. Half the time when WP gets hacked, it wasn't brute-force anyway...it's the fact that the thing is so poorly written that it's full of security holes.

That account is not suspended. If you see a suspended page, please clear your cache.

I don't know of any reason why it shouldn't work, but nobody's ever asked this before. Django in general can be a bit of a pain though. Lets see if Krydos knows how to do this (I would've done the same thing as you, just modified the paths).

Please create a new topic for that request. This one is a year old, for a different issue, and long since resolved.

Unblocked.

That account could not be unarchived due to a server error (database owner already exists). Krydos can usually get these to unarchive, but your username will change when this happens. Lets see what he can do.

It's actually pizzan2. Unarchiving...

Unblocked.

Done.

Note that outlook.com sends our invite to spam. Check your spam filter for it. If you can't find it, please provide us a different email address and I'll be happy to resend it.

Done. It should start working again within the next few hours.