I have a web page on a Linux server I administer, running Apache 2.2. This server is visible to the outside world for some other services.

I would like to configure Apache so that a given virtual host is only visible from inside the local network, so I can deploy a web application to get feedback from other people in my organization. I reckon this has to do with the Allow directive, but my experiments are not going well.

How can I alter my config file to achieve that? Should I change the firewall configuration as well?

  • Are you using a private (non-routable) IP address such as or public (routable) IP address for your server?
    – closetnoc
    Commented Mar 19, 2014 at 16:48
  • The server has a public IP address, and I can connect to it from outside the work network - from home, for example. The colleagues' computers all have local IP addresses of the 10.*.*.* type.
    – Btz
    Commented Mar 20, 2014 at 0:01

4 Answers 4


People landing in this answer, please note that this is specific for Apache 2.2.

Apache 2.4 has deprecated these directives.

The new way is using the module mod_authz_host and the Require directives. (link)

In Apache 2.4 you should do

<Directory /var/www/ncp-web/>
  Require host localhost
  Require ip
  Require ip 192.168
  Require ip 10

, and remove all Allow directives.


Easy. Just set something like this within your main configuration or your virtual configuration:

<Directory /var/www/path/to/your/web/documents>

  Order Deny,Allow
  Deny from all
  Allow from ::1
  Allow from localhost
  Allow from 192.168
  Allow from 10
  Satisfy Any


The <Directory></Directory> statement basically says, “Use these rules for anything in this directory. And by “this directory” that refers to the /var/www/path/to/your/web/documents which I have set in this example but should be changed to match your site’s local directory path.

Next within the <Directory></Directory> area you are changing the default Apache behavior which Allow’s all by default to Order Deny,Allow. Next, you set Deny from all from denies access from everyone. Follwing that are the Allow from statements which allows access from ::1 (localhost IP address), localhost (the localhost itself). That’s all the standard stuff. Since access from localhost is needed for many internal system processes.

What follows is the stuff that matters to you.

The Allow from for 192.168 as well as 10 will allow access from any/all network addresses within the network range that is prefixed by those numbers.

So by indicating 192.168 that basically means if a user has an address like or they will be able to see the website.

And similarly using the Allow from for the 10 prefix assures that if someone has an IP address of or even they will be able to see the content.

Pretty much all internal networks in the world use either the 192.168 range or something in the 10 range. Nothing external. So using this combo will achieve your goal of blocking access to the outside world but only allow access from within your local network.

  • What is Satisfy Any supposed to do in this case? I know nothing about all of this but when it was present in my scenario, i could access the page (I used <Location /path>) from an external network. Removing it however fixed my issues. It wold be nice to understand why this was the case as it was slightly concerned that i could access the page even with the rules in place. Commented Aug 10, 2016 at 17:24
  • @liamnichols As explained here: “Allows the request if any requirement is met (authentication OR access).” Commented Aug 11, 2016 at 0:06

Add this section inside your virtual host directive:

<Location /mypathurl>
    Order deny,allow
    Deny from all
    Allow from

Replace your IP above. This should not be used for financial level security, FYI.


I do not know how you have your network setup, however, I am assuming somethings to try and make a better answer.

Let's assume you have a have a small office with a DSL connection. You would have a static public IP address or a block of addresses assigned to your line, a DSL modem, and a firewall. Without getting into the details of how this happens, I will get to the important part.

You should be using NAT (network address translation). This allows the public IP addresses to reside on the WAN (Internet) side of your network and use private IP addresses (like within the network on the LAN side. This is standard operation procedure. If you host a web server within your network, then you would use port forwarding or other similar mechanism) to point any web traffic to your web server.

In this standard scenario, your internal computers would all use the private IP addresses.

Assuming that you have a similar standard network setup, you would change your computer IP address from a public IP address to a private IP address. Your network may have DHCP setup where your computer can request an available IP address. This means that instead of specifying an IP address, you select to use DHCP and an IP address will be assigned. If DHCP is not available, then you would have to check some other computers for a private IP address space that may be used and select an IP address within the space that is not used. You can specify this unused IP address in your network setup. This should keep your system from being seen on the Internet.

  • I thought about it, but it's not a practical solution. There are services on that machine that have to remain visible to the outside, and in any case I plan to make the web application visible again in a few days - no point in revolutionizing the network layout just for a few days. What I can work on, however, is things like the Apache configuration.
    – Btz
    Commented Mar 20, 2014 at 10:34
  • If you have a firewall, then you can close some ports to that IP address.
    – closetnoc
    Commented Mar 20, 2014 at 15:36
  • Firewall settings could be used, but that is really overkill. Apache has built in functionality to deny or allow based on IP address & other related criteria. See my answer for more details. Commented Aug 17, 2014 at 18:56
  • @JakeGould Firewalls are not necessarily an overkill solution. I do know Apache really really well. However, there are HTTP filtering options in most good firewalls that help without putting a load on the server itself. As well, while Apache is excellent, it is not without fault. As well, port accesses including alternative port accesses can be manipulated using a firewall so that some web services remain public and others are only accessible within the LAN.
    – closetnoc
    Commented Aug 17, 2014 at 21:53

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.