Krydos

Well, the numbers I've given you are a rank of your memory usage versus all other users on your site so there aren't really units. Basically the server just keeps track of which accounts are using how much memory and cpu as a percent of available memory and cpu throughout the day, and then it sorts it by who used the most cummulatively. Being ranked #1 in either category doesn't even mean you're going to get suspended either. We don't have any maximum cpu or memory usage restraints for accounts. As long as the server is running well no one gets suspended. If the server starts to crash or run slowly due to lack of memory then the highest memory usage account gets suspended. If the server is about to crash or is running slowly due to the cpu being pegged out at 100% then the highest cpu usage accounts are suspended. That way one account isn't allowed to hog all the system resources and cause poor performance for all the other thousands of accounts sharing your server. As far as figuring out what script(s) are using the most memory it's pretty much impossible for us to give you any useful information because CMS' generally are all accessed through index.php which includes dozens if not hundreds of other files, so from the point of view of the server's log files that index.php file is using all of the resources. Generally though, the more plugins and the more addons you install on your CMS the more memory it will require all that extra stuff.

There are already thousands in not millions of paid hosting options available in the world. There are very few good free webhosting options. Most free webhosts are just a gimmick that is owned by a paid host that they use to hook people into their service and then they do everything they can to get the person to upgrade to a paid plan instead of the free plan. Heliohost is different. We don't have any paid hosting plans so none of our users will ever be extorted into paying us money for anything. The other thing that I've seen occur quite often is a new free webhost will start up with a similar "nothing but free accounts" philosophy similar to us, but they quickly find that it's not a very profitable business to be in and they quickly switch to paid hosting or run out of money and shut down. Heliohost is different. We've been in business for nearly nine years now offering nothing but the best free webhosting on the internet. Not only that, but we're quite profitable so you don't have to worry about us shutting down for lack of money. If you appreciate good, fast, reliable, free hosting without any tricks or bullshit then you're in the right place.

It's not a security issue, but like I said already I think it would be useless for you since you wouldn't be able to use it whether it was installed or not.

Since you didn't really answer this question I'll ask it in a different way. Why can't you just use one port?

I skimmed through the documentation quickly, and it looks like it would be useless for you even if I did install it because you don't have shell access. Besides it's probably less work for you to just install the dependencies manually rather than messing around with a dependency manager, but that's just my opinion.

What do you need three ports for?

Have you tried deleting or renaming your .htaccess file?

Stevie is averaging 266 ms response time for the last week, and about 262 ms for the last month. If you're not familiar with units of time 60,000 ms would be the response time if your claim that it takes a minute to load a page were true. That's decently fast for a free host with 99.9% uptime. I DO know how to make both Johnny and Stevie faster though. It's actually really simple: Delete about 90-95% of the accounts on both servers and start charging the remaining 5-10% like $10 a month or so. Simple solution to a simple problem. It's the exact same solution that most all of the rest of the web hosts in the world use, but that's what makes Heliohost different. We offer ridiculously good service (in my opinion) all for free.

Here is your cpu and memory usage as a rank among other users on your same server. 1=highest 4=three users are higher than you, etc. Larger numbers mean less load and less chance of being suspended. date cpu mem 2014-02-10 10 4 2014-02-09 14 4 2014-02-08 11 4 2014-02-07 15 3 2014-02-06 13 3 2014-02-05 12 2 2014-02-04 13 8

If you're talking about a directory inside public_html then you can just delete it. FTP or cPanel's built in file manager, etc will work.

The domain is working just fine. The problem is with this file: /home/jeret/public_html/.htaccess Which contains the code: RewriteCond %{HTTP_HOST} ^rehabsecurity\.com$ [OR] RewriteCond %{HTTP_HOST} ^www\.rehabsecurity\.com$ RewriteRule ^/?$ "http\:\/\/rehabsecurity\.heliohost\.org\/" [R=301,L] For whatever reason you redirect visitors to rehabsecurity.com to the nonexistant domain rehabsecurity.heliohost.org and that's why you see the error message you do.

The addon domain “condellenterprises.com” has been created. The problem you were having (after the nameservers got set correctly) is that when you create an addon domain the system actually first creates a subdomain, and then parks the new domain on the subdomain. The error message you were getting was letting you know that the subdomain you were trying to park your addon domain on already existed on your account. I first deleted the subdomain, and then tried parking your domain for you and it worked just fine for me. Let us know if you're having any other issues with your account.

It's probably because you already have an account on Stevie with username nasahrva, main domain http://nasahrvatska.info/ , created on 2013-07-28, and last logging into on 2013-07-31. If you wish to reactivate your existing account type the username nasahrva into this link http://www.heliohost.org/home/support/scripts/renew

Yeah, we are planning on upgrading the default version, but since people can run Django 1.5+ anyways it's less of a priority. Have you read through http://www.helionet.org/index/topic/17025-successfully-runnig-django-151-on-heliohost/ ? Another thing to consider when upgrading versions like this on systems hosting tens of thousands of domain is that anyone running a functional django 1.3 website would no longer work.

That just means that most of the emails aren't actually leaving the server. Trying to send upwards of 6000+ emails per day still puts massive load on the server and bogs down all of the other accounts from sending legitimate emails. Hence the suspension.

Ok.

If setting a domains nameservers gives a "not authoritative" response like that you have two options Contact your registrar's customer support or find a way to override the error and set your nameservers to ns1.heliohost.org and ns2.heliohost.org Change your main domain http://www.heliohost.org/home/support/scripts/domain to the domain you're trying to add, and after 24 hours or so you should be able to set the ns records correctly. Obviously option #1 is faster and easier and better, but some registrar's are dumb and won't let you set your ns records to whatever you want. Usually it's some sort of a scam to try to sell you hosting. Option #2 gets around their shenanigans if they won't work with you. Good luck!

Seriously? http://infinitylegends.tk/ 25,000+ posts? I think the bots have taken over. Stop the bots and the load will follow suit.

Glad to hear you're doing better. Hope things continue going your way.

The most common reason for brute force protection like that from your own IP address is if you save a password in an FTP client or some other client that logs into your account and then change your password without updating the FTP client. Most FTP clients are pretty dumb and will just try over and over with the wrong password until your account is locked down. I don't see any brute force protection on your account currently so you should be good for now.

To switch servers follow these instructions http://wiki.helionet.org/Moving_your_account Please note that having two accounts (or more) without prior permission could result in all of your accounts being suspended. Stevie is our stable server and to help keep him stable we limit the number of new accounts that can be created each day. Once signups for that day are full you need to wait until the next day to create your account. This link http://bybyron.net/helio/sign-up.php might help you to figure out when signups reopen.

Please post the following information: Your cPanel username Your main domain The server that you are on Your cz.cc domain you are trying to park

You can check the uptime/downtime and load records for December 5th with this link: http://heliohost.grd.net.pl/monitor/archive/?2013-12-05 Johnny looks about the same as he is on any normal day. Whether downtime can cause an email to not be received depends more on the sending email server than the receiving. Even 1 minute of downtime on the receiving server can cause mail to not arrive if the sending server is poorly configured. Standard practices say that a sending email server should retry sending failed messages for up to 3 days, but some administrators cheat to reduce load and use a much shorter retry time. If the sending server only tried once and Johnny was experiencing high load at the time then yes it is possible that the email would never arrive, but most of the time it shouldn't matter because the sending server will try sending it again later resulting in a delay of the email not in a complete failure.

Please clear your cache.

Please clear your cache.