500 Internal Server Error

[jccoelho99]

Hi there,

 

I've recently updated my .htaccess file to mirror the one I'm using on my live site and

am now getting a 500 INTERNAL SERVER ERROR.

Don't know if I'm missing directives that have to be there or if it's a Heliohost problem.

Unfortunately I never backed up the original .htaccess before updating.

 

Please excuse my newbness.

 

Just wondering if there's directives I have to put in there to get the site back up?

Or are you encountering problems atm?

Again my current .htaccess is working fine elsewhere.

 

Would really appreciate.

[Byron]

You can check the Error log at your cpanel and see if it tells you why or you can post your htaccess code here and I can tell you why.

 

[jccoelho99]

Ty Byron I think I'm learning web mastering the hard way lol

I found the following error in the log

 

[Fri May 21 02:36:49 2010] [alert] [client 41.220.42.18] /home/jccoelho/public_html/.htaccess: Invalid command 'php_value', perhaps misspelled or defined by a module not included in the server configuration

 

So commenting (#) any directives related to php seems to have sorted it.

 

So are we not allowed to configure php from .htaccess on your server?

Also I think I saw some <post ??> <limit ??> directives in there.

Can I ask what they were about?

 

Much appreciated. Maybe I'll setup a mirror on Stevie and configure my other site to redirect here sometime.

Then I can maybe mask the URL Apache sends to the client from here (still using .htaccess) and no one will notice a thing?

The point being Stevie being so fast when not under attack at least

 

But it might a long while until then really need to do some development and leave .htaccess files alone.

They're addictive!

 

I found my backup!

 

Here's the directives I was on about

 

<Limit GET POST>

order deny,allow

deny from all

allow from all

require group authors administrators

</Limit>

<Limit PUT DELETE>

order deny,allow

deny from all

</Limit>

 

Do we need to use limit? Also the Auth entries should I leave them there or can I block them out?

[Byron]

Our PHP is setup under suPHP - it isn't compiled under a DSO. In other words, the php_value directive does not exist under our Apache.

 

I've never used the Limit directives and I've always just deleted what is default in our htaccess files and never had any problems.

[jccoelho99]

Our PHP is setup under suPHP - it isn't compiled under a DSO. In other words, the php_value directive does not exist under our Apache.

 

I've never used the Limit directives and I've always just deleted what is default in our htaccess files and never had any problems.

Thanks. I've just done the same.

It looks like limit was used for some sort of password protection.

I can't get the code back in anyway (getting a 13 permission denied error accessing the password file)

Hope it's a good thing lol

 

Just wanted to ask is the Options directive disabled?

 

It seems I can't use it without getting a Server error.

 

[Byron]

Just wanted to ask is the Options directive disabled?

 

It seems I can't use it without getting a Server error.

 

Not that I know of. I'm using this right now in mine:

 

Options All Indexes

 

What exactly are you using that gives you a 500 error?

 

 

[jccoelho99]

Options +Indexes +MultiViews +FollowSymlinks

 

Instant 500 Internal Server error :/

[Byron]

I tried your code on my site without any problems. Try it without the + signs and see if that works for you.

 

Options Indexes MultiViews FollowSymlinks

 

 

 

 

I take that back. I did seem to have some problems. Try it like this:

 

Options All Indexes MultiViews FollowSymlinks

 

or better yet

 

Options All MultiViews

 

Options All takes care of everything except Multiviews.

 

 

[jccoelho99]

Thanks Byron sry about the delay.

I think maybe I read somewhere that you can't mix the +- syntax when they're absent elsewhere.

So maybe it's all starting to make sense now?

 

I'm feeling less of a newb now