rvt

I do believe you are trying to sign up at the wrong time.

If the server is on GMT-7 time and you are GMT+8 then there is a 15 hour difference between you. Hence, if you ever try and sign up with a time in the "AM" then of course the sign up limit will have been reached. You need to sign up at 15:00 or 3PM your time (difference of 15 hours from server time).

What is the domain name of your account here?

SMF's v2 is still a release candidate, not a production level release and they even say they suggest not installing it on production sites. Not sure what version of the v1 series is there but I'm sure it is one of the recent releases.

Afraid.org is asking you to upgrade to the branded name servers because they make money off that. Have you followed my instructions so far?

Alright, stergos my recommendation is you sign up with an account here: http://freedns.afraid.org It is free to sign up with them. The advantage of using them over HelioHost's DNS is that if for some reason HelioHost is down for an extended period of time, your DNS records will still be available and you can even change them to point to other hosting with minimal wait time for propagation.

 

Once you sign up with an account, you need to create the appropriate records for your domain. At a minimum you should create 1 A record titled "@" (without quotes), the lowest TTL you can set, and a IP address of 216.218.192.170. You should also create a CNAME record titled "WWW" (again, without quotes) and point it to "@" (your A record). Then, at your domain registrar change your name servers to the ones provided by afraid.org.

 

If you have issues OR if you have email @e-hacking.com set up, post back and I can walk you through those steps.

 

Thank you very much I will try it! Off course I don't have any idea how to start, but my first question is:

I sign up and I try to add my domain, to the current table say's:

 

"Also... make sure you are ONLY using the above nameservers unless you know what you are doing.

If you include other nameservers at your registrar besides the listed above, and not all nameservers are properly setup to be in sync with each other, your site may experience intermittent downtime."

 

I cannot place their 4 nameservers because I use 2 For Helios and is only 2 left.

I'm newbie with dns I afraid I will screw up.

 

My email address is webmaster@e-hacking.com or "stergos4" to skype. I appreciate all of you, thank you for trying help me!!!

Once you add the appropriate records over at afraid.org, you no longer need to use the HelioHost name servers. If you post back with the name servers it is telling you to use, I'll try and check their records for accuracy.

Alright, stergos my recommendation is you sign up with an account here: http://freedns.afraid.org It is free to sign up with them. The advantage of using them over HelioHost's DNS is that if for some reason HelioHost is down for an extended period of time, your DNS records will still be available and you can even change them to point to other hosting with minimal wait time for propagation.

Once you sign up with an account, you need to create the appropriate records for your domain. At a minimum you should create 1 A record titled "@" (without quotes), the lowest TTL you can set, and a IP address of 216.218.192.170. You should also create a CNAME record titled "WWW" (again, without quotes) and point it to "@" (your A record). Then, at your domain registrar change your name servers to the ones provided by afraid.org.

If you have issues OR if you have email @e-hacking.com set up, post back and I can walk you through those steps.

Perhaps integrating the server load in to the Forum layout (say, top right maybe?) would remove the need to have it in anyone's signature?

As Geoff pointed out, you can't edit the DNS settings in this way in a shared hosting environment. What you are trying to do is access the Configuration file for the DNS service for all of the accounts hosted here. From a security standpoint that just can't happen.

Since you do have your own domain, you should be able to move your DNS away from Heliohost with a similar effect. If you switch to your Domain Registrar's name servers and then set the proper records there, you should be able to avoid DNS issues when Stevie goes down. If you provide your domain name I can try and provide more detailed steps.

I think you are in over your head if you want my opinion. Regardless, do you have your own domain or are you operating off of a .heliohost.org subdomain?

I do agree Ubuntu does not seem to be playing nicely with WebDisk and FTP. Only option at the moment seems to be cPanel's built in file manager.

Or maybe someone else working on the site keeps changing the password on you.

Everything looks good and is working from my location.

If you want your sites to be accessible with the "www" prefix, you should add CNAME records pointing to @ (Your A Record)

Just create an A record pointing to the IP and you'll be good. You don't need any extra URL's or anything.

What you are trying to do is definitely possible. I have it set up that way for my domain here. I suggest you look up "Virtual Hosting" to get a better understanding of what is going on. In short, many domains hosted on 1 IP address that the server then determines which files to send based on domain.

Tested with both "purchased" and self signed SSL certificates. Guide to reproduce problem is below:

The following steps are performed on a separate Linux machine or through cPanel's "generate key/cert" options

Step 1: Generate RSA Private Key either through cPanel or with the following Linux command - openssl genrsa 1024 > host.key

Step 2: Generate Certificate either through cPanel or with the following Linux command - openssl req -new -x509 -nodes -sha1 -days 365 -key host.key > host.cert

Step 3: Go to the SSL install page on cPanel (http://www.heliohost.org:2082/frontend/x3/ssl/install.html) and copy/paste your key and certificate in to the appropriate fields. If generated by cPanel, they should appear automatically.

Step 4: Select the domain from the drop down menu

Step 5: Click the "Install Certificate" button

cPanel then displays this:

If I could get cPanel to dump more info I would but it doesn't. Tried waiting 24+ hours for an Apache restart and no luck there either.

Tried when server load was 9...no luck. Will monitor server load over the next couple hours and if I see it lower will try again.

@raman: localhost is correct as localhost applies to whatever system you are on. When installing Joomla, you want to use MySQL on the local machine (server). If you are still having issues, PM me your log in information and I'll install it for you.

Also, for some reason, when I install the certificate, I get an error saying "error from ssl wrapper:"

 

And then it fails to install...

Confirmed, happening to me as well.

Instead of waiting on enough people to commit, you could use http://www.osqa.net/ and host your own Q/A website for HelioHost support.

The problem with it is has to be hosted by HelioHost. The advantage of StackOverflow is it is hosted by them. There was also an offer on the table to let The Host Helpers handle the support operations. Again, the advantage there is that it is hosted "away" from Helio Networks so if those go down, support is still available. Ultimately, I think any solution which moves it off of Helio's servers is a good one.

What if I run only two jobs with that frequency?

 

I mean, these are very small scripts, like few KB, I can't believe bandwidth would be the problem?

As jje said, it isn't about bandwidth as much as it is about server load. On HelioHost, there are 20,000+ accounts on the server. On paid hosting, this number is more in the 300 range. Thus, server load is lower on paid hosting and users can put more strain on the system. Unfortunately it is just the reality of the situation.

I don't think so man, this is shared hosting and that is way to often for a free shared host. If you are looking to run something with that much frequency, my recommendations would be to either: go with paid hosting. Personally, I've used HostGator Share Hosting for a situation similar to yours and found that it works great. You might also want to consider getting a Virtual Private Server. HostGator's VPS Plans are fully managed by their administrators but give you the flexibility of having your own machine that you can run scripts on as often as you want. If you are really serious about your site, I'd go with the VPS option (specifically Level 4 VPS @ HostGator).

Personally, I don't think you are going to be able to find a reliable, free host to fit your needs.

If your files are becoming corrupt when uploading via FTP, I would recommend trying FTPS (Secure). What might be happening is some bad router is corrupting your files, and FTPS ensures that your files are not corrupted during transfer.

However, be aware that FTPS and SFTP are not supported on HelioHost's servers.

Did you wait the 24 hours as posted on the page?

 

uhm, yeap for the hosting. if i go to s5ent.heliohost.org, i can already see my root index, but if i go to www.s5ent.com, i get the account queued page. right now my settings in my domain provider's zone file is a cname for "www" to "s5ent.heliohost.org" and a url forward from "s5ent.com" to "www.s5ent.com"; and my cpanel setting at stevie.heliohost.org is a parked domain for "s5ent.com" with the defaults. this parked domain setting i haven't waited for 24hrs yet.

 

do i have the right settings that i can wait on? if not kindly lemme know what needs to be done :]

 

thanks for the immediate reply!

Hi,

I can confirm for you that your set up method should work. I have set up a domain here this exact same way. You seem to have made a typo in your entry of your domains IP address. Using the DNS Utility I see that the IP of your Heliohost subdomain is 216.218.192.170. However, you have set the IP of your .com domain to 216.218.192.70. You will need to change this in order to get your domain working.

Be aware, it takes 24 hours from the time you enter a domain in cPanel for it to move out of the "Account Queued" stage because Apache must be restarted and this only happens on a daily basis.

As a follow up question, it is not recommended to add an A record pointing to Stevie's IP in CO.CC's settings because it can change and the co.cc nameserves have not way of knowing it, where as the heliohost nameservers would know when stevie's IP changes. Is that the reason or am I missing something?

Pretty much. The advantage of using an A record on other name servers is if Heliohost goes down, your DNS does not also go down (which means you couldn't send/receive email, even through Google Apps, etc). Also, should you decide to move web hosts, changing an A record can propagate across the internet in a matter of hours where as changing NS records could take 48+ hours.

Not your fault. Caused when server load is high (which, at times, is more often then not). Only solution is to move to another host.