wolstech

We don't specifically prohibit them. However, if you allow public uploads, you are responsible for what people upload and you only get 500MB of space, so a lot of things won't fit. Also, if any of the files are infected, you might get suspended for malware when the AV scan runs.

I'm not seeing any account with that username. Did you receive a second email saying the creation failed?

Did you create the subdomain? They need to be created in cpanel and take 24 hours to start working once you do. Subdomains for accounts on Johnny may take longer. Also, you used commas between the 1 and channel. Those should be periods, like http://1.channel.heliohost.org

You're welcome.

Try it now.

Ns2 is down and hasn't worked in months...Does your registrar requires two working nameservers?

We don't offer that for security reasons. It would affect every one of the 1000+ users on the server. What specific reason makes you think this is necessary?

You're on Johnny. Accounts on Johnny can take up to 5 days to come out of the queue. Just give it some more time. If it still isn't working on Friday, let us know and we'll look into it further.

You were suspended for running 3 cron jobs. The limit is 2 executions per day. Your account has been unsuspended.

Any unsuspension beyond 3 for the same reason is up to us, but we're usually pretty flexible as long as you're actually working on fixing the software issues that cause it. We have the limit because some users will just ask to be unsuspended over and over without fixing the problems. High load affects every account on your server (in this case Stevie), so letting people continuously do it over and over would just lead to performance issues and downtime. If you get suspended again before the admin posts the file causing this, we can unsuspend you again once the information is posted. It's not a hassle to unsuspend an account (it takes 30 seconds or so). As for recovering the content of an account that's suspended permanently, our official policy is that we don't make/keep/provide backups, so what you're doing is the best course of action...make plenty of backups on your own.

We don't monitor bandwidth. You were suspended for excess resource usage (RAM and/or CPU) last time. Your suspension this time is for the same thing. Your account has been unsuspended. Do be aware that a third suspension for this reason will be permanent. This support request is being escalated to our root admin. He may be able to provide you with the name of the file that caused the load.

If it keeps asking, it's generally because the username or password is incorrect. Usernames must be in lower case, and passwords are case sensitive. Your username is mellokc. Try resetting your password. If it doesn't reset, let us know and we can reset it manually and email it to you.

Those apparently didn't spew deprecated warnings in 5.3 for some reason. Those functions are the exact reason why my software doesn't work in anything newer. I get tons of warnings about the MySQL commands. The commands are scattered throughout every one of the hundred or so files that make the system up. My software is all custom and I don't have time to rewrite it using mysqli (which has no benefit aside from new php version support anyway when you develop procedurally as I do...)

This support request is being escalated to our root admin. The admin needs to run that command for you to unblock you.

Theres not too many hosts that support php newer than 5.3. This'll change with time, but right now we only support 5.3, as do many others. The reason many places aren't upgrading quickly is because the newer php versions are not completely backwards compatible like the previous ones were. If we upgraded, many users would be left with broken software. For instance, the software I use won't run on 5.5 at all, and works but spews tons of deprecated errors on 5.4.

There is no solution beyond waiting for the repair to be finished. @yashrs: There seems to be something going on in the past day or so. My site crashed 14 times yesterday in comparison to the ~3/day it's been experiencing. It died on me several times last night while trying to do some work.

See http://www.helionet.org/index/topic/18875-stevie-mysql-common-questions-and-problems/ First one in the list. The 500 error is likely just whatever software you use choking on a crashed database server. It goes away because cP restarts MySQL after a few minutes when its down.

It probably hasn't been deleted fully yet. Give it 24 hours then sign up again. If it fails a second time, try a different username.

Did you receive an email with an error message? If so, can you post that email? As yashrs said, the account doesn't exist. Either way, try signing up again.

Please clear your cache.

The _vti_ folders and _private are frontpage extensions. Go here and uninstall them for all domains listed: http://stevie.heliohost.org:2082/frontend/x3/fp/index.html Those folders will go away automatically once uninstalled. The images folder can be removed if empty. Leave the cgi-bin folder alone.

This support request is being escalated to our root admin. An admin will probably have more information on the spam that got you suspended.

The password reset issue is probably one of the more common issues people have. Some people don't get the mail because a few email providers flag the reset mail as spam (some will delete it without putting it in Spam). Other times people get confirmation codes that don't work...that happens for many reasons, but the most common reason is because your account is inactive or suspended when you reset the password. As for reliability, I've never had any major issues with reliability here. I've been here on Stevie for 3 years. I'm running 2 websites and numerous backend/internal use systems in my account. Aside from the MySQL issue in February (granted it still isn't fixed), I've never had an issue. There's downtime for maintenance overnight on occasion, but it seems to last like 10 minutes. For the price we pay, it's the best offer out there. You are on Johnny it seems, which is the reason we're down so much for you. His uptime is indeed terrible. If you need the reliability, you should move to Stevie. @yashrs: When resetting passwords, you should send it to the registration email address showing in the acp, not by PM. EDIT: Byron beat me to it...

He's on Johnny, and Johnny has plenty of space in / (only 79% used). /usr on the other hand is full, and the swap is nearly full.

This support request is being escalated to our root admin.