Ashoat

We had a problem with our error_log processing. Are you seeing anything in your error_log now? This is what I'm seeing: [Mon Apr 05 11:12:00 2010] [error] got here 1!['/home/sonny/public_html/bradweb/', '/usr/lib64/python2.4/site-packages/setuptools-0.6c5-py2.4.egg', '/usr/lib64/python2.4/site-packages/MySQL_python-1.2.2-py2.4-linux-x86_64.egg', '/usr/lib/python2.4/site-packages/setuptools-0.6c8-py2.4.egg', '/usr/lib/python2.4/site-packages/flup-1.0.1-py2.4.egg', '/usr/lib/python2.4/site-packages/pysqlite-2.5.0-py2.4-linux-x86_64.egg', '/usr/lib64/python24.zip', '/usr/lib64/python2.4', '/usr/lib64/python2.4/plat-linux2', '/usr/lib64/python2.4/lib-tk', '/usr/lib64/python2.4/lib-dynload', '/usr/lib64/python2.4/site-packages', '/usr/lib64/python2.4/site-packages/PIL', '/usr/lib64/python2.4/site-packages/gtk-2.0', '/usr/lib/python2.4/site-packages'] [Mon Apr 05 11:12:00 2010] [error] [client 128.208.7.226] mod_wsgi (pid=26666): Exception occurred processing WSGI script '/home/sonny/public_html/bradweb/dispatch.wsgi'. [Mon Apr 05 11:12:00 2010] [error] [client 128.208.7.226] File "/home/sonny/public_html/bradweb/dispatch.wsgi", line 13, in application

Tidy has been added to our build for our next recompilation. However, because cPanel requires recompilation of Apache in order to recompile PHP (don't ask), we won't be able to immediately start offering Tidy service. It'll be available upon next recompilation, which will probably be in a few months.

I went through that tutorial, but I think it was wrong on a number of counts (including the coding errors it claimed existed, and the installation method it used). Regardless, I figured out how to make it work and Ming should now be installed for PHP. Is it working for you guys?

Wait, why can't you use port 80? Do you have another web server running on your computer? Note that incoming and outgoing ports are not the same.

I'm pretty sure it's working. phpinfo() is showing --with-pdo-sqlite, so it's definitely installed.

The tests are ongoing.

I've patched the main issue that caused this. I blame cPanel.

No. Like I said, we block all ports we don't use.

Yeah, got the donation. Thanks

Yes. HelioHost will always be free, as it has for the past five years.

You can't point their nameservers to us, but you can establish the necessary records there if you have enough control. You'll have to figure that out on your own, though. Anyways, open a new thread. This thread is not for those issues. This domain doesn't seem to be pointed to HelioHost. You are not supposed to have two accounts. It is in clear red text on our homepage.

Why not just run the software on your home server on another port?

You're breaking our rules.

That account doesn't seem to be in our system. Please open another thread if you think it should be.

No problem

I'm not sure if changing the key will require an Apache restart, but if it does you will need to wait 24 hours.

That can't be your username. Usernames can't be longer than eight characters.

Most outgoing ports are blocked. Why do you need this port?

Okay, start a new topic once you know what you're going to need.

Hey guys, This latest downtime was because I asked my university's CS department to try to hack HelioHost given an SSH account (I'm experimenting to see if we might be able to offer it in the future). Basically, I'm running a security audit to see if I can patch all the holes. However, I didn't make it quite abundantly clear enough that they weren't supposed to down the server. Hopefully won't happen again. Thanks, djbob

You have to edit your .htaccess file. This shouldn't be too hard, but this isn't a hosting issue.

I'm not here to teach you Apache directives. I'm here for support issues. If something is wrong with your hosting account I will fix it, but the rest of it is your job. Try here.

Okay, you've been granted a dedicated IP.

You'll need to modify your .htaccess file to add the rewrite rules for the https prefix.

Please post your problem in this thread.