wolstech

I wouldn't worry about it since it doesn't really help security that much. Being a free host, anyone could sign up and just check most of that info in cPanel. Plus, things like PHP expose themselves in the headers too. Pretty much all hacking incidents we see are account compromises that result from insecure user-installed software (usually WordPress) or weak/stolen passwords.

Those no longer work due to the damage from the crash. Escalating so a root admin can delete it for you.

This support request is being escalated to our root admin.

If you created the account through the new system, it should've given you that to start with I think. The method I listed was for existing accounts or ones created through the classic site. Escalating.

We recently offered everybody an increase to 1GB if they verified their email address. You should be able to get this increase yourself by signing into our website here:https://heliohost.org/?_=new After that, select the option to validate your email address. Once you complete the verification, it should automatically give the increase. If it does not, or you don't see the option to verify, let me know and I'll escalate it for you.

twnn.heliohost.org is now working, however the file index.php does not exist. Please clear your cache and verify that index.php is in your public_html folder.

This support request is being escalated to our root admin.

Duas.ga is now configured and is already working for me. Please clear your cache again.

What is the account name and email address in question?

I'm not seeing that domain in our system. You probably parked it too soon and it didn't park successfully. Can you please re-park it (remove first if present) and let me know when you've done so? Once you do that, I'll verify it parked properly, then you just have to wait the 24 hours for it to work.

That's just saying it can't find a custom error page for the forbidden error. It's normal if you don't have one set up. If you'd rather show a pretty forbidden page that matches your site, you can set up some custom error pages in cPanel. You specify them by their error code (e.g. 404, 403, 500, etc.). That can be done here: http://stevie.heliohost.org:2082/frontend/x3/err/index.html

That account is still queued. Accounts take 24-48 hours to start working.

They've probably gone invisible. Can you list the database names so I can have krydos take a look?

I see an internal server error. Please clear your cache. The server error is likely caused by whatever software you have installed.

This should be fixed now. Can you try it again?

You just have to wait until 2am unfortunately. Back when I joined, registrations were on pacific time. I live in eastern time, which meant I got up at 3am to register...most of us who've been around here long enough have done it at one point. You can see the state of sign ups here: http://heliohost.grd.net.pl/monitor/ Note that Stevie is the only server that currently accepts registrations. Tommy is not yet released (he's still in private beta), and Johnny is crashed.

Nodejs is not supported. We only support technologies that host through apache. Nodejs is a standalone own server.

That error doesn't appear for me in cPanel, and MySQL is working fine for me. Try logging out and in again. As for the lost database, we probably don't have anything. The data loss would be from the MySQL crash yesterday. InnoDB looks to have died again. InnoDB is extremely sensitive...just look at it wrong and it crashes, while we have never lost MyISAM data in our 10 years in operation. I'll escalate this to see if Krydos happens to have backups of the innodb databases for some reason, but odds are we don't have anything to restore.

Topic split and escalated.

It's related to yesterday's database server crash. InnoDB broke again. Escalating.

That requires InnoDB support, which is read only on Stevie due to damage from the crash earlier today. As a result, you can't install that right now. The InnoDB database engine, while nice for its advanced features, is quite unreliable and crashes if you so much as look at it wrong. It also has a habit of taking all your data with it when it goes. InnoDB has crashed 6 times in two years, each resulting in significant data loss. On the other hand, MyISAM is much more stable and has never lost any data in the ten years we've been in operation. I'd recommend using software that can use MyISAM database tables (you'll need to do some research, if I remember right phpBB and SMF were the two big ones that could do this easily). If you don't wish to do this, wait until the server is repaired, then install xenforo. Just make sure you make database backups frequently, as you will likely need them the next time the database server crashes.

There was an active phishing site on your account at the time it was suspended. We can't show you the contents because doing so would give you access to the data collected by the phishing site. Very often, legitimate accounts that get suspended for phishing occur because of a security hole or weak/compromised password. A hacker exploits these to get in, and once that happens, they either send spam or (as in this case) phishing sets up shop on your account. We then catch it (or someone reports it), and the account gets suspended. Please create a new account.

Looks like InnoDB might have crashed again... Escalating.

3 cron jobs, so yes. Unsuspended.

Stevie's MySQL was down for a few hours earlier. It appears to be working now.