Ashoat

Okay, I've got it working. You have a few errors you'll have to fix (for instance, you need to switch some paths in settings.py), but you can continue to debug by yourself from here. The issue was that Python needed a temporary directory to store eggs (modules, ie. MySQL and PgSQL).

Your account needs to be validated before it will be active. Until then, you will not be able to login and your URL will display a suspended message. After validation, make sure you type your username in lowercase (ie. jd201, not JD201).

We have a two cron a day limit, so as long as your script doesn't use an inordinate amount of resources and isn't run hourly or anything, you should be fine.

Yes.

Try again and see if it works now. If it doesn't: what is your HelioHost username and domain?

Turns out I forgot to finish programming the "Other" domain in the signup script. Try again now, it should work.

You can just add diablosa.co.za as a parked domain in your cPanel, or you can have me change your domain. PM me your username, domain, and the email you signed up with to do this.

Yeah, you're welcome.

I would think that you can. Go ahead and try. Out of curiosity, why did you leave X10?

Not in binary, but it could have been sent with the wrong MIME type. My text editor could have mistakened it as did Dreamweaver.

This looks like a cPanel error. I have posted in their forums, and will hopefully get a response soon. I'll let you know as soon as I get an update.

This is an extremely weird error. Although you did have the mistake of using "Context-type" instead of "Content-type", when I fixed that the 500 errors were still coming up. I copied the contents of a working Hello World into your file and it still didn't work. I did the opposite with your original text, and that worked fine. When I copy your original file, however, the new copied file won't work either. Just create a new file with the same text and see if it works for you.

Can you tell me what the actual domain is? Also, what is your HelioHost username?

http://www.helionet.org/index/index.php?showforum=73

OK, the port has been opened.

Are you making sure to type your username in all lowercase? The username field in cPanel is case-sensitive.

Sorry about that. Should be working now.

You can use a .heliohost.org subdomain. You need an existing top-level domain if you want to use a TLD - ie., if you type in some random .com that you don't own in the registration page, your site won't work. However, we can grant you free .heliohost.org subdomains

We are currently experiencing hardware issues. I am working day and night to get the server working again. See this topic for more information.

The issues are still occurring. After lots and lots of hours of debugging, I have concluded that the current server crashes as well as the "hacking" that happened earlier were hardware issues. To be specific, it seems like Stevie is having memory issues. Memory issues are really hard to detect and often result in really bizarre problems (which I thought must have been a hacking last time). I am currently working with our colocation provider to see if we can confirm these issues, after which point I will request a replacement RAM stick under Stevie's warranty. Here is a summarization of the issues I have experienced so far: - About three weeks ago Apache went down on Stevie. When I attempted to restart it, Apache informed me that its port was in use. When I tried to check which application was using the port using netstat –p, lsof, fuser, etc., my SSH session just froze. The shell connection was still there, but the server was unresponsive. I was able to restart these frozen sessions, however, by reconnecting. After playing around, I found that anything involving a PID, or access to the /home partition would crash in this fashion. I concluded that somebody had hacked Stevie, and requested that he be shipped from the datacenter to my house so I could reinstall the kernel. - After Stevie arrived, I started him up to see if the issue could have been specific just to OpenSSH. I was surprised to find that not only were the issues completely gone when directly logged in, but they did not appear when connected over SSH. After strengthening the server’s security a little bit and checking for rootkits through an external kernel, I shipped the server back. He seemed to work fine. - However, soon after the server came back online, I started to notice more issues. Apache was generating large amounts of coredumps (about one every four minutes). After investigating the coredumps, I found that httpd -t (a configtest, equivalent to apachectl configtest) would generate a segfault once in about twenty or so times. What’s more, it would segfault in completely random places; there was no consistent pattern. I now conclude that my server has memory issues.

Is the bold, red "not for HelioHost support" not enough for you? >_< We are currently experiencing network issues. Your account seems like it hasn't been activated yet. I'm working on the network issues as we speak.

Why not use a standard port? Why do you need a unique port?

I think ponyboy is interested in downloading from HTTP/FTP, not uploading.

Did you make sure to point the domain's nameservers to HelioHost? Make sure to set them to: ns1.heliohost.org ns2.heliohost.org

You would just upload your file to somewhere in public_html using FTP. Then, you can navigate your browser to http://yourdomain.blah/yourfilelocation. For instance, if I uploaded test.zip to public_html/test, then I could download it at http://mydomain.blah/test/test.zip.