wolstech

Database is likely invisible from the repairs last year. Escalating.

Seems to be working for me now as well. As tjoene said please clear your cache.

@Byron: Can you unblock me in Stevie's firewall please? I think I just managed to block myself for DoS using the Open All on the phishing scanner... :unsure: Speaking of that...can these IPs be whitelisted so this doesn't happen to me? * 204.13.205.35 * 69.242.123.95

You could try moving to Stevie, but I don't know how well his postgres works (it is newer if I remember right). I was able to create a database and user in cPanel and view/edit it in PhpPgAdmin though, so it appears to be working...

We changed it to MyISAM intentionally. InnoDB has a past history of being extremely unreliable here. It crashed a while back (on both servers no less!) and was broken for well over a year. It was actually just fixed a few months ago. It was read-only for everyone, and the mysql server would crash for everyone on the server every time someone tried to edit an InnoDB table. A ton of users had to convert their databases to MyISAM at that point, or have their databases manually restored when the server was fixed. Everyone had to recreate their database users too. In fact, because of it, I don't even have a single InnoDB table on my account anymore that I can test with! I dropped all of mine when the server was finally capable of doing it without crashing...

I'm seeing that as well. Says your active though and resuspending/unsuspending you isn't fixing it. Can you rename or delete the .htaccess file in your public_html folder?

The browser looks at the number and will actually attempt to connecting on port 9090 (which will fail)...htaccess is processed server-side, so unless you can specify a different port in your browser, and still somehow get the browser to connect on port 80, this will not work.

This support request is being escalated to our root admin.

@sagnik: No. It could be used to force https (if you have it) but you cannot redirect requests sent to other ports since our firewall would keep any connection not on a normal web port from ever reaching apache for the htaccess to process it.

Your account was suspended for causing high server 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. If you still see the suspended page, please clear your cache.

You have to try just after that time of day (midnight U.S. Pacific), so just after 8am UTC. We close the signups every day once a certain number of users have registered so the server doesn't get overloaded. Also, you can't have 2 accounts, so you'll need to delete your Johnny account before you can register on Stevie.

That's normal since you are on Johnny. Johnny is designed to be a more experimental server. It's intended to provide extra functionality at the expense of speed and uptime. If you need a reliable server and can do without Ruby, ASP.NET, and Java, I would recommend you move to Stevie. We are in the process of implementing a new server that will offer Johnny's features with Stevie's reliability, however that new offering will not be available for a little while yet.

Stevie's been up and down all day today. 17 alerts from uptime robot for my domains, and http://heliohost.grd.net.pl/monitor/ is showing abnormal behavior for Stevie as well. Also, it looks like NS1 died around 0830 PST as well, shortly after the first three hour period of instability (which began around 0400). When I was last able to get into cPanel, his load was through the roof and cPanel's pages were taking minutes each to load. Can you please look at this Krydos?

I see: That can be caused by three things: You forgot to change the config file for your software to match the new database user information or the username or password you entered in the file is incorrect. The host name should be localhost. You forgot to assign the user to your database, or assigned it to the wrong database. Stevie MySQL is down (it's not) PHPMyAdmin does not use the database user, so it doesn't test that. The fact you can see it there though tells me the database is fine. The permissions on the user are not the issue, you would get a different error message if they were (usually in the form "SELECT command denied for user X@localhost for database Y") The 0MB in cPanel is normal and can be ignored. All of mine show 0MB too, but have tons of data in them and work fine.

This support request is being escalated to our root admin.

Stevie and Johnny are not being replaced, it will be in addition to them. So far, the hope is when the new box comes online, it will host Cody and a server that will have Johnny's features but Stevie's stability and restrictions on load and signups so people who need a stable Ruby/ASP.NET host have a box to use. Those two won't even use all of the resources on the hardware either, so there will be room to eventually add other options as well...a multiversion PHP server was brought up in the discussion.

Probably an invisible database from the repairs last year. Escalating. Database is fairtrek_ft...

You're welcome! Let us know if you need anything else. We'll be glad to help

Your account has been manually unsuspended. As for the script...yeah, our website broke this morning. See http://www.helionet.org/index/topic/23112-sql-error-on-heliohostorg/ if you want to follow that issue.

Heliohost.org is indeed showing a #1062 error. Escalating.

We will be getting a new server with newer software (likely 5.6), but nothing is really decided beyond the hardware at this point. I would expect a few months wait though. If it comes online sooner, you'll know since it will be announced and promoted when it does. For now, you will need to keep the older version, as there are currently no plans to upgrade Stevie or Johnny beyond 5.4.

It's not just FTP connections, it's any connection. There's no hard limit, though most blocks seem to occur when there are around 25 connections to our server from a single IP Address. You were blocked for DoS, so it can be anything that causes you to open too many connections. FTP is the usual cause, but other causes do exist like broken software not closing connections when finished, or having too many devices on your home wifi that check a mailbox on your account too frequently. If it was FTP, it happens especially when transferring a lot of things at once. Set your FTP client to only open a max of ~3 connections at a time during uploads. Also, never download large quantities of files via FTP (e.g. to back up your account), as many clients will attempt to download them all at once (one connection per file) and get you blocked. If you need to download a lot of files (more than ~20) off of your account, use the cPanel file manager or download an archive of your entire public_html folder using the backup functions in cPanel and extract the files you need from the backup.

You're welcome Please let us know if you need anything else. We're always here to help!

I've split your issue from today and moved it to customer service. Byron usually fixes these, he'll see it there. http://www.helionet.org/index/topic/23109-cant-access-site-firewall-issue/

Firewall blocked you most likely. Seeing that you're likely still fixing your site, it's probably FTP usage. Byron usually fixes these. Moved to customer service.