Ashoat

Your account was deleted earlier today for not being updated for more than 3 months. You were warned of this about fifteen days ago. Did you not recieve an email?

That's probably part of the problem, but you can't expect me to be an expert. I mean, most server admins go to college to learn about these things.

Restarted. Why can't FTP, PostgreSQL, and the Mail daemons stay online?

Your account does not show that you logged in. What skin do you use?

Holy cow :blink:It took me a few clicks... but I'm being tougher now

Your account is not expired; it is about to expire. All you need to do to alleviate this situation should be to just log into cPanel.

Banned for 7 days for spamming.

Try again.

"Mispelling" is a misspelling

Naynesh, stop being hypocritical. We're talking about you. In case you didn't notice, he was going sarcastic.

Probably not, considering I doubt this kid's telling the truth. If he attended a university, as he claims he does, then he would know way better grammar.

The thing is default to 30 days for a reason. Naynesh, you have horrible grammar and you're spamming. I doubt I'm going to give a domain, even if you get 5000 Helions, as most of them were from spam. You're blatantly breaking our rules and not even trying to fix your issues.

I'm sure. If you care so much, why not just buy a domain instead of spamming our forums for one?

Formatting is there to accentuate part of a post - what is the point if you accentuate it all? Stop using formatting incorrectly. You only get a domain when you buy it. Hosting is seperate from a domain.

You don't need to edit posts that have reasonable grammar. Also, I am never on heliohost.net.

Read the topic again carefully and see what I told you to do.

The only thing I got out of that post was an inaccurate assumption that I giving out free Adsense vouchers. If you want me to answer anymore of your questions I expect a post I don't have to try so hard to comprehend.

If you don't know what FTP is you probably shouldn't be using this service.

Nobody is up to the job of admin, and I am not letting this community decide anything. I put that message there because nobody paid any attention to it before, so now it actually mentions the most common issues. I am considering some software modifications to make the board more idiot-proof.

As I said before, you don't suck at grammar. For instance, the post am I responding to is fine. You just didn't care before.

We now have a new server configuration. That's good, for a number of reasons: It uses Apache 2.2, which is faster, more modular, more up to date, etc. We now have mod_mono, which means we now offer ASP and ASP.NET support. We now have suphp (which had caused the majority of 500 error problems; see below) which heightens security for PHP scripts by associating each PHP thread (each file being executed) to its user for quick problem identification and elimination. It also has other features that increase security. We now have mod_security, which makes our server more secure. We now have a few new PHP 5 modules, including the requested XMLRPC module. If any of you are wondering why we went down for about a day last week and then had numerous server errors, here is a description of all the issues we encountered: When I first tried upgrading to Apache 2.2, cPanel set us up with a configuration that was incompatible. Consequently, Apache refused to load for some time. Eventually I downgraded to Apache 2.0 just to get the server running. Soon I realized what the problem configuration with the help of a helpful cPanel forum member; after this I upgraded the server to Apache 2.2. The 500 errors (by the way: 500 is an error code, not a quantification) were caused by suphp. This modification follows stringent security protocols that a lot of our files were incompatible with, so I had to make some adjustments. Originally, it checked CHMOD levels and would not allow execution if a file was CHMOD'd to 777 - I disabled that feature. To get the signup function working was a different matter, however - it involved some complex configuration, considering that the signup folder is located in a secure location. I had to set suphp's docroot to the server root, I had to tell it not to check for a vhost's files being located in the vhost's docroot (the folder is alias'd across the server for access by the heliohost.org vhost), and I had to set the uid and gid of the folder and the files inside it to a lower-privileged user. Anyways, now everything is working. If you don't understand the above, don't try figuring it out - it's server admin stuff, mostly intended for other server admins who have similiar issues and need a solution. Anyways, have fun with the new configuration. The only real new feature is ASP/ASP.NET support, which should be quite exciting.

Ask me again with proper grammar and I'll answer your question.

Are you kidding? You're saying you're sorry about bad grammar in a post with bad grammar?

It's easy to check just be looking at the error_log For some reason you added C-style comments to your .htaccess. .htaccess file use shell-style commands (ie. "#" instead of "//"). 500 errors are usually caused by your .htaccess file - try to check there first.

Oh, does Northern English not have capitalization, periods, apostrophes, commas, and other grammatical symbols then?