wolstech

It makes sense. The more popular it becomes, the more crap they shove in to keep the userbase growing, and the more sloppy the code becomes as they rush those features out the door to meet demand. Moodle has always been a mess honestly, but it's gotten worse lately.

Please check your PMs.

I'll set a Lily account up shortly and send the information by PM.

Krydos might be able to help identify the cause of the load. As for VPS payment, if you can't use PayPal, we can also accept skrill or even cryptocurrency.

There are ways to learn something without phishing...

Gone.

Is the account valpros yours? That's the account that has that domain on it, and it's active. Please be aware you're not allowed to have two accounts, so valpros needs to be be deleted if you want the other account back.

Try it now. I think I got it correct...

What IP needs access?

We don't allow remote access by default. Krydos has to specifically enable it if you want it. Since the username and database name are in the error, I'll escalate this to be set up.

Apache didn't come back up after the server crashed again (it crashed and was found turned off, apparently the same as the other day). What needs to be done to start Apache since WHM and /scripts/restartsrv_httpd refuse to let me restart it (gives a message about a build in progress)?

Turns out yesterday's crash was the same way. It's been turned back on again and is booting up.

My guess is someone is crashing it. The weird part though is that the Ricky VM is *turned off* (?????), whereas I'd expect a panic or it to be unresponsive if crashed. I'm not sure if this is intentional (Krydos could be doing something) or if something happened. I'd restart it, but I don't know if K is doing anything with it/its disks at the moment so don't want to mess with it. We're actually planning to rebuild Ricky in the near future anyway. In the meantime, once it is running again, would you prefer to be moved to Johnny?

You need to use NS records pointed to ns1.heliohost.org and ns2.heliohost.org. The shared IP is 65.19.141.67 since you're on Johnny, however our service will not function correctly if you aim a domain here with it. Also, be aware that if you use Cloudflare, you'll probably want to remove it. It's not fully supported and has been known to cause all sorts of weird issues, especially relating to email functionality.

Failed: Account Restore Failed: “Account failure: Failed to create the account: A database owner with the name “ceomega” already exists.” [ 20166][RESTORE:1 ]: Account “ceomega”: Account Restore Failed: “Account failure: Failed to create the account: A database owner with the name “ceomega” already exists.”

This error is almost always poorly written code (or on rare occasion having way too much traffic). You're opening too many MySQL connections at once. Best practice is to either open->query->close all together, or to open exactly one connection and reuse it for all queries your script will make. Also, always make sure to explicitly close connections with mysqli_close() when you're done with them. Don't just assume they'll close because the script died (though they should). Also, abandoning a handle to a connection (e.g. you let $dbc go out of scope or you unset() it...) doesn't close the connection, just leaves it open in limbo with no way to access it until something else causes it to close (typically PHP exiting). Finally, worst case is you could move to Tommy since that server currently has no connection limit for MySQL, though that's subject to change if abused.

Try renaming or deleting your htaccess file so it is ignored.

Indeed it was for too many resources. Whatever you're running is either broken or way too heavy for Tommy. Please fix that quickly. Unsuspended.

It's because you're forcing SSL on a domain that does not have a certificate installed. Remove and reinstall your certs and wait a few hours and it will work.

It got auto-banned because we have reason to believe it was intended to be used for bank phishing. Also, you already have another account anyway and aren't allowed to create another account (users are only allowed to have one account). If it hadn't gotten banned for phishing, both of your accounts would be suspended for having more than one account instead.

Weird you get that message, it was just inactive on my end, not archived, and it just let me unsuspend it. Unsuspended.

Your account was suspended because Wordpress is causing too much load. I have unsuspended your account, but please try to limit the load you put on our servers as it slows down not only your site, but the sites of all other HelioHost users sharing your server.<br /><br />This is really common for Wordpress. It can cause massive amounts of load even if you're hardly getting any traffic to your site. Wordpress is also incredibly insecure and very easy to hack. We see Wordpress accounts get hacked all the time and usually the hacker sets up a phishing site on your domain. We strongly recommend using any software other than Wordpress.<br /><br />Something that might help is this simply static Wordpress plugin. It will speed up your site, reduce the load you cause, and reduce your chance of getting hacked. If you try it let us know how it worked out for you.<br /><br />If you insist on using Wordpress you might want to consider purchasing a VPS instead. VPS hosting gives you an entire virtual server to yourself, including no load limits, a dedicated IP address, and full root access. Wordpress sites load relatively slowly on our shared hosting, but they will be much faster on a VPS.

We no longer offer the .org free subdomains. It has to be .heliohost.us now instead. Also, the script has a bad habit of not working on the heliohost.us subdomains anyway, so we usually have to change them manually. I've manually changed your domain for you. Give it a few hours and rogeriobsoares.heliohost.us should work.

While FTP use is probably the easiest way to open too many connections, in theory a bloated website with lots of assets could do it too, especially if a browser tried to download them all at once (or if you opened/refreshed multiple tabs of it at the same time). While not this particular incident, I've definitely gotten myself blocked during a DOS just by having a few tabs open with various pages from one of my applications.

Unsuspended.