Comments on: Errors with .htaccess : Site Down with 403 Forbidden Errors

By: Narlax

Narlax — Mon, 04 Apr 2011 07:34:12 +0000

well….thanks to all for sharing your ideas

By: online

online — Fri, 03 Apr 2009 03:25:34 +0000

You will probably want to create an error document for codes 404 and 500, at the least 404 since this would give you a chance to handle requests for pages not found. 500 would help you out with internal server errors in any scripts you have running. You may also want to consider ErrorDocuments for 401 – Authorization Required (as in when somebody tries to enter a protected area of your site without the proper credentials), 403 – Forbidden (as in when a file with permissions not allowing it to be accessed by the user is requested) and 400 – Bad Request, which is one of those generic kind of errors that people get to by doing some weird stuff with your URL or scripts.

By: Michael Brode

Michael Brode — Thu, 24 Apr 2008 12:13:47 +0000

Hello friend,

You can visible hidden files (.htaccess) in FileZilla 3 as follows:
– You go under the menu item “Server” and activate “list hidden files force”
– The following dialog close simply by klick OK. Done.

Greeting

By: MPLS

MPLS — Sat, 02 Feb 2008 04:36:59 +0000

I had a similar problem. I was doing some testing and have installed PHP 5 on a development server. I had a site installed on the server that was working correctly, complete with quite an elaborate .htaccess file handling many redirects and rules. However, after installing PHP5 it turns out any php file I tried to view just returned a 403 Forbidden error. I began to scratch my head. Searching on Google didn’t immediately bring up a solution either. However, I eventually narrowed it down to the fact that I needed to add Options +FollowSymLinks to my .htaccess file. That solved it all.

By: Matt Van Dusen

Matt Van Dusen — Sat, 18 Aug 2007 14:09:23 +0000

In my experience with Dreamhost, they do mean well, and usually fix it right the first time – but this shows that yes, they are human. They can make mistakes, However, they will tell you when they do something, they don’t beat around the bush, and if something requires action from you (that they can’t just control themselves from the support center), they will give you step-by-step direction on the matter, whether it is upgrading your webapps (a clear-cut case of “staying on top of things”) or telling Google that they don’t need to make 50,000 hits every hour (a clear-cut case of “our servers can handle it…. can yours?”).

Granted, Google pretty much IS the internets these days, but even they can be blocked with very little effort. :P

By: Mr. Nosuch

Mr. Nosuch — Mon, 04 Jun 2007 17:31:41 +0000

Thanks for posting this. It helped me figure out why our forums page rank went to 0. It killed our ad revenues and search results.

I’m really pissed that Dreamhost would do this without contacting me. They have a fine contact/support system, yet when they decided to make huge changes like this, they don’t let me know?

Really, really annoying.

By: Josh

Josh — Thu, 24 May 2007 05:08:42 +0000

Blocking Googlebot goes too far. For people who make a living from search engines it is unacceptable.

By: Jack

Jack — Fri, 04 May 2007 16:27:07 +0000

I use Dreamhost as well. They disabled two of my sites at different times because they said I configured my .htaccess file incorrectly, causing it to hit the server over and over again. In actuality, it was googlebot spidering my site of 20,000 pages. Seriously, they can’t handle googlebot? To solve the problem I went into Google Webmaster Tools and slowed down the crawl rate for spidering my site.

By: Daniel

Daniel — Fri, 27 Apr 2007 11:23:15 +0000

You have this site on a shared hosting plan over DreamHost?

I am a client of them as well, but I only host smaller sites there. Not reliable at all from my past experiences.

By: Ed

Ed — Fri, 27 Apr 2007 01:37:37 +0000

but I can’t remember to close my html tags apparently… hehe