Skip to content
NYC Tech Tips

NYC Tech Tips

Tech Tips From a NYC System Administrator

  • Home
  • About
  • Downloads
  • JB Network Design
  • Toggle search form

500 Internal Server Error

Posted on April 30, 2011 By ninjatechnyc 2 Comments on 500 Internal Server Error

Got a personal website hosted on Godaddy that all of a sudden started giving me 500 Internal Server Error:

I have the domain and hosting at Godaddy – Economy Linux hosting. I use WordPress as the front end. Not the WordPress setup they offer, but I uploaded my own WordPress files, setup a MySQL db, and configured everything manually. I use the site to host family pictures and videos. I haven’t made any changes in a month however all of a sudden I’m getting 500 Internal Server Errors.

During the course of my investigation, I found out it was due to my .htaccess file. The site worked without it, but why? It worked fine before!

Turns out it was the following line in the file:

# disable directory browsing
Options All -Indexes

I commented it out, and everything worked fine. Not sure if it’s a Godaddy issue or an Apache issue. Probably the former.

But I would think it would be prudent to disable directory browsing. However, what’s weird is that I have similar setups with Godaddy, including the Options All -Indexes, and have no issues…yet.

opinion, tech tips Tags:500, apache, godaddy, htaccess, Internal Server Error, linux, Wordpress

Post navigation

Previous Post: Switch To GNOME From Unity
Next Post: ID Theft – And So It Begins…

Comments (2) on “500 Internal Server Error”

  1. naeem says:
    July 24, 2011 at 9:07 am

    I aslo have domain and hosting at godaddy, but i am using Joomla CMS, having same error. I checked Error logs from ftp file manager and i got .htaccess file in error folder and it says : [Options +Indexes]
    Can any one help me how can i get rid out from this internal server error, although it dose not come all the time. some time get this error

    1. nyctechguy says:
      July 25, 2011 at 9:54 pm

      If you have the .htaccess file, try renaming it temporarily to see if that fixes your problem. If it does, then you know it has something to do with the error you are receiving. Try maybe to redo the .htaccess file, adding portions at a time to isolate the culprit.

Comments are closed.

Search

Tags

adobe Amazon antispyware antivirus apache Apple AT&T blackberry browser China computer data breach Dell dilbert dogbert email encryption facebook faulting application FB firefox firewall flash drives freeware godaddy google Hack Identity Theft Internet Explorer iPhone linux malware Microsoft paypal phishing privacy recommended reading scam security software tech support ubuntu virus windows Wordpress

Archives

  • April 2021
  • September 2020
  • July 2020
  • June 2020
  • May 2020
  • April 2020
  • June 2017
  • May 2017
  • December 2016
  • November 2015
  • June 2015
  • June 2012
  • February 2012
  • January 2012
  • December 2011
  • November 2011
  • September 2011
  • July 2011
  • May 2011
  • April 2011
  • March 2011
  • January 2011
  • December 2010
  • October 2010
  • August 2010
  • June 2010
  • May 2010
  • April 2010
  • March 2010
  • February 2010
  • December 2009
  • July 2009
  • June 2009
  • May 2009
  • April 2009
  • February 2009
  • December 2008
  • November 2008
  • October 2008
  • July 2008
  • June 2008
  • April 2008
  • March 2008
  • January 2008

Copyright © 2021 NYC Tech Tips

Powered by PressBook Dark WordPress theme