views:

2386

answers:

6

Hi Everbody,

I am getting this error message while trying to access a wordpress blog which is installed in a directory. Is this due to .htaccess or something? Any help is appreciated.

'The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator, [email protected] and inform them of the time the error occurred, and anything you might have done that may have caused the error.

More information about this error may be available in the server error log.

Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

Apache Server at xxxx.com Port 80'

+2  A: 

It sounds like you're getting some sort of PHP error but PHP isn't set to display errors. You'll want to check your Apache logs for detailed error info.

The mostly likely culprit is that you're missing some prerequisite for running WordPress, although all you should really need is Apache, MySQL, & mod_rewrite.

Mark Biek
+1  A: 

An HTTP 500 error could be caused by a great many things. Have you changed your .htaccess file recently? If you try to use a .htaccess feature that is disabled on your host, that is one possible cause.

Matt Kane
+1  A: 

Unfortunately it could be anything. Do static pages on the site work properly.

Have you checked the server logs.

I think it is likely to do with php. If static pages are there then possibly your config for wordpress is incorrectly configured or files missing.

Has php be working? Did the blog work and then stop? Did you get through the install process?

Cheers Stephen

Stephen Baugh
+4  A: 

This is almost always a problem with your Apache configuration. Errors originating in PHP won’t trigger the Apache 5xx handler, which is what you’re seeing.

Unfortunately, without more information, your problem is impossible to diagnose. I’d recommend that you:

  1. Check the logs. First thing! It should give you a better idea where your problem is.
  2. Stop and restart Apache. If there is a problem with permissions on something Apache needs write access to (logs), it could completely fail to start. This should give you the proper motivation to fix the problem, particularly if there are other VirtualHosts on that Apache.
  3. Move your .htaccess file(s) somewhere else. If Apache works, you know it’s a problem with that file.
ieure
Actually these errors sometimes occur because of problems with PHP, so it might be the culprit after all.
frgtn
A: 

Some more points

  • Blog has been running successfully. Just observed this problem since yesterday.
  • Blog is in a directory so it works something like this www.xyz.com/blog. Apparently www.xyz.com is working perfectly.

Update on logs

Getting these two errors in the logs:

  1. File does not exist: /home/directory/public_html/500.shtml
  2. /home/sub-directory/public_html/sub-directory/.htaccess: RewriteCond: bad argument line '%{REQUEST_FILENAME}!-f'
  3. /home/directory/public_html/sub-directory/.htaccess: # without matching # section

How do I restart apache on cpanel ?

Daksh
Can you post the contents of the .htaccess file?
Mark Biek
Did you set up a new plugin or change the perma link structure? Again it's hard to trouble shot without a copy of the .htaccess, but I would be look at what has changed since you set up the blog.
Stephen Baugh
A: 

Hi Folks, I am facing the same issue currently. The wordpress blog suddenly stopped working one fine day. I was not playing around with any configuration at all. It worked one day and not the other.

Replacing the .htaccess with a blank one has not worked either for me.

Chirag Jog