Krydos

Probably malicious users like usual. You'll know for sure by watching this forum http://www.helionet.org/index/forum/81-suspended-and-queued-accounts/ the keyword will be "causing high server load."

I don't see any reason on our end why you wouldn't be able to see your site. Your IP isn't blocked by our firewalls, and your site loads fine for me without a proxy. Sometimes countries -- most notably China -- block random IPs from being viewed within their borders, but that seems unlikely because your country doesn't have a history of that. It could also be your ISP doing the blocking. Perhaps an overactive firewall on your computer, but that also seems unlikely since it sounds like you have multiple computers and they probably aren't all set up with exactly the same antivirus/firewall version and everything. It's kind of a mystery I guess. Out of curiousity can you view this site? http://krydos.tk/

Done.

It depends on what the VPN control panel requires, but I know others have successfully done it before.

Done.

I don't understand why it needs to be deleted or closed. Can you explain that? FYI: Topics posted in customer service or suspended accounts are closed after 48 hours of inactivity if they are marked as [solved], because those topics generally are specific to one account or one specific problem that affects all accounts on a server. Unresolved topics in customer service where the Heliohost staff are asking for information like username or domain and the topic creator never responds are closed after one week and marked [inactive]. If the unresolved topic has all the necessary information, but all the staff who have worked in it are stumped or it will take more than a week to resolve are escalated so they won't be flagged as inactive, buried, and forgotten. Topics posted in questions are kept open because someone might have the same question someday and want to bring an old topic back by adding more information or asking for more information on the same topic.

So basically 3 steps. Purchase a certificate, get a free (trial version maybe) certificate somehow, or self sign a certificate. Purchase a dedicated IP address from us for $12 by sending the money through paypal to admin@heliohost.org. Once the payment is received we can grant your account the dedicated IP. Visit this link http://stevie.heliohost.org:2082/frontend/x3/ssl/index.html and go through the steps to install the certificate from step 1.

It sounds like your database user that you're using to connect to that database doesn't have the correct permissions granted. What is your Heliohost username?

Using the automated delete script in the wiki article http://wiki.helionet.org/Moving_your_account does not work when the server is offline, and will post an error saying that your username or password is incorrect. This is because it can find your account in the main account database, but cannot connect to the server (since it's offline.) However, if you let us know what your username is we can delete the account manually so you can recreate your account your account on Stevie.

Since the server is offline it won't be able to send emails to you no matter how many times you request a password reset. I'm a little confused how you have been resetting your password anyways because the reset password page is offline. If you've been using the password reset box at http://stevie.heliohost.org:2082/ then that only resets passwords for accounts located on Stevie. http://johnny.heliohost.org:2082/ would reset passwords for accounts located on Johnny if it was online.

There is no account in the system with the username 'bluefox'. Perhaps you already deleted it?

Accounts are not and will not be deleted or suspended on Johnny until after he has been back online and stable for a while.

Done.

That script only lets you delete your account when the server is online because it checks to see if you can successfully log in first before it deletes. Since the server is offline it won't work. I have deleted your account manually.

Stevie has had 18 minutes of downtime in the last week and 0 minutes of downtime in the last 4 days. Something else must be going on. Have you tried visiting your site through a proxy or from a different computer?

httpupdate.cpanel.net is the url that cPanel uses to upgrade itself. Those IP addreses if you open them in a browser all lead to the latest version of the cPanel software. As far as how to see your site's visitors IP addresses I would recommend installing google analytics or something similar because they have a lot of powerful tools for analyzing the data instead of figuring it all out yourself. Another option is to add some simple code to your pages to log the IP addresses. Perhaps something like this http://www.ebrueggem...site_access_log

Your account is currently using 263 MB; 262MB of which is in public_html. I also noticed that you now have at least two accounts. Each user is allowed to have one account. Which account would you like to keep and which account(s) would you like me to delete for you?

As predicted your site is working now. If you're still seeing the queued page don't forget to clear your browser cache or view your site through a proxy to see what the rest of the world is seeing.

If you're referring to MySQL max_user_connections that error is most likely because your code has bugs in it that don't close the open MySQL connections. The server settings are fine, and there are hundreds of websites that have way more traffic than your site and use MySQL more than your site and they don't get those errors.

A warning system for people before they get suspended for high load, high mysql, too many emails, exceeding 500 MB limit, etc. is one of the projects we were working on before Johnny decided to take a break. I took a quick look at your account and there are literally hundreds of accounts causing more load than yours so I wouldn't worry too much.

If you post what the problem was and what you did to fix it, then it would greatly benefit anyone in the future who is experiencing a similar problem and finds this post through a search.

That quote was from this post http://www.helionet....dpost__p__83359 on September 24th. Quite a lot has changed since that small 10 minutes downtime almost two weeks ago. Stevie currently has 99.82% uptime. If you need uptime we recommend you create your account on that server. Furthermore, we don't guarantee any level of uptime. In fact the terms of service http://wiki.helionet.org/Terms, which all creators of accounts must agree to prior to the account being created, plainly state: You're free to do what you want. I've looked through the AdminCP and the Moderator sections looking for any deleted posts by you and cannot find any. As a policy we only delete spam posts for like viagra or other weird bot stuff like that. We edit posts to remove profanity, but apart from that we don't censor anything that anyone wants to say about us. I have no idea where all this anger is coming from. Yes, I think it's incredibly frustrating that Johnny has crashed too, but ranting and raving on the forums does not encourage the administration to spend more time volunteering their efforts to keep Heliohost functional. In fact instead of working on Johnny I have spent a few minutes responding to you instead. What is a better use of my time do you think? In my opinion this behaviour is like if we were instead giving away free ice cream on a hot summer day. Then your cone breaks and you don't get to eat your ice cream so you start screaming that no one else should try the free ice cream either. I don't know, maybe it's not a very good analogy, but you could read this if you want to http://s3.zetaboards...p=7200&t=304216 EDIT: All issues resolved through PMs.

Everything looks like it's set up correctly, but the domain says it was added about 12 hours ago. Did you change your main domain earlier today or something? Anyways, give it another 12 hours (to make a total of 24 hours) without changing anything and then let us know if it's still not working.

You had multiple php processes that had been running for 11+ hours. You might want to check your code to make sure there isn't anything that would cause it. I killed the processes for you.

Does it work now?