Thread: Block IPs via HTACCESS

First of all, is the use of .htaccess efficient for blocking out ranges of IP addresses?
And second, what would the file look like? What is the correct syntax?

I want to block out entire IP address ranges from one of my forums and I'm leaning towards using .htaccess to do it.

Can someone point me in the right direction or post an example or something, please?

Originally Posted by Zap

First of all, is the use of .htaccess efficient for blocking out ranges of IP addresses?
And second, what would the file look like? What is the correct syntax?

I want to block out entire IP address ranges from one of my forums and I'm leaning towards using .htaccess to do it.

Can someone point me in the right direction or post an example or something, please?

I think this is exactly what you need Mr Zap!

Block IPs with .htaccess

Thanks CS!

Would anyone know, does blocking IP via cPanel cause more strain on the server than using .htaccess?

Cpanel just creates the .htaccess file doesn't it?

Originally Posted by GRIM

Cpanel just creates the .htaccess file doesn't it?

Yes and/or adds to it.

Originally Posted by Zap

Thanks CS!

Would anyone know, does blocking IP via cPanel cause more strain on the server than using .htaccess?

When you add an IP to block via cPanel it just adds to your already existing .htaccess file or creates a .htaccess file if you don't have one. I recommend actually doing it the cPanel way since cPanel sort of "takes over" your .htaccess file regardless.

vectro added 1 Minutes and 49 Seconds later...

Also related to blocking IP addresses using .htaccess:

blockacountry.com will generate entire block lists of countries that you can cut and paste into your .htaccess file. However, mod_geoip for the Apache webserver is more accurate and up to date if your host has that (or if you have your own server and install it yourself).

Originally Posted by GRIM

Cpanel just creates the .htaccess file doesn't it?

I thought that might have been the case, but wasn't 100% sure.

Originally Posted by vectro

Also related to blocking IP addresses using .htaccess:

blockacountry.com will generate entire block lists of countries that you can cut and paste into your .htaccess file. However, mod_geoip for the Apache webserver is more accurate and up to date if your host has that (or if you have your own server and install it yourself).

Thanks for blockacountry.com.
I'll have to check them out.

I have a VPS, but I'm only experiencing problems on one website.
How is mod_geoip used and can it be used for one website while all the others on that server are unaffected?

Originally Posted by Zap

I thought that might have been the case, but wasn't 100% sure.



Thanks for blockacountry.com.
I'll have to check them out.

I have a VPS, but I'm only experiencing problems on one website.
How is mod_geoip used and can it be used for one website while all the others on that server are unaffected?

mod_geoip is installed as a module for the Apache web server. I don't have much experience with VPS but I suspect an admin would have to install the module into the web server for you. mod_geoip is only called when certain directives to block specific countries are placed in .htaccess. Therefore, you would only place those directives on the sites that need country blocking.

the blockacountry.com way creates very long cut and paste lists. It makes .htaccess big pretty quickly. The mod_geoip way is only uses a few lines.