Krydos

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.

Solved topics are automatically closed after about 48 hours. Unsolved topics in customer service are closed after about 7 days of inactivity. Questions are never closed. Just open /home/hooper/public_html/.htaccess and copy/paste in the code. You can backup the file first to save your working copy as something like .htaccess.old so you can restore it if it doesn't work the way you want. Worst case scenario with editing .htaccess files is you get a syntax error and your site shows a 500 error. The reason the account was deleted was because you never logged into it. When you lost that domain and you asked me about it I told you to log into the account by visiting http://heliohost.org/ and logging into cpanel at least once every 30 days. Since you failed to do that the system flagged the account as inactive and sent you an email letting you know, and after several months of inactivity the oldest inactive account are deleted to make room for active accounts. You could have kept the account active without a functional domain forever if you had followed my instructions. Sure. The dedicated IP address covers all the domains on that account. Your SSL certificate may not cover all the domains though. If your purchase a more expensive certificate, like a wildcard certificate, you can have SSL on all of your subdomains like store.lisanet.com, forum.lisanet.com, blog.lisanet.com, images.lisanet.com, etc. The standard (least expensive) certificates only cover one domain regardless of how many domains happen to be hosted on that IP address. That's the reason I originally set you up with two accounts because you wanted to have SSL on two unrelated domain names so you needed two accounts each with their own unique IP address.

This support request is being escalated to our root admin.

The account zept has been unsuspended.

Here is your cpu and memory usage as a rank amongst 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 1-26 9 5 1-25 8 5 1-24 8 5 1-23 14 4 1-22 17 5 1-21 10 8 1-20 11 8

Is it working now?

Java isn't enabled on that account. In order to use Java/JSP you must

LMGTFY: https://docs.djangoproject.com/en/1.3/intro/tutorial01/