Forum Moderators: phranque
xx.xx.xx.135
xx.xx.xx.142
xx.xx.xx.137
xxx.xxx.133.139
xxx.xxx.125.xxx
xx.116.xxx.130
131.xxx.xxx.xxx
xxx.139.xxx.xxx
xx.xxx.143.xxx
127.0.0.1
After trial and error I found 2 typos that caused the problem:
RewriteCond %{REMOTE_ADDR} ^63\.240\.227\.11[2-9]¦12[0-7] [OR]
-should have been:
RewriteCond %{REMOTE_ADDR} ^63\.240\.227\.(11[2-9]¦12[0-7]) [OR]
--and
RewriteCond %{REMOTE_ADDR} ^63\.240\.248\.12[89]¦13[0-9]¦14[0-3] [OR]
-should have been:
RewriteCond %{REMOTE_ADDR} ^63\.240\.248\.(12[89]¦13[0-9]¦14[0-3]) [OR]
By not putting parentheses around the final elements of the statements I effectively blocked all users that had a 112 - 143 anywhere in their IP address.
A few of those IP's belonged to google, hopefully they will forgive me and come back.
Yet another reason to watch what you type very carefully.
--EDIT I forgot to ask the question.
Is google going to come back?
Good advice, there... Check your work!
Google will come back as long as you have at least one incoming link to your site. Since they crawl a fairly large portion of the Web, they've seen all the possible problems you could imagine with Web site configurations -- and have developed rather forgiving approaches to error-handling as a result.
You could always "call" Googlebot back by submitting your home page to Google - See their Web site. While it's usually better to just let them find you, I think using their submit page (once) is useful when trying to recover from configuration errors like this.
Jim