Let’s say you have:
- A server with an ip address (like
xxx.xxx.xxx.xxx) - A domain name (like
example.com)
And you want to be able to reach your web server (Apache 2.4 in this case) via your domain name (example.com) but you want to block access via ip address (so that when you type xxx.xxx.xxx.xxx in the address bar, it doesn’t work).
- Connect via SSH to your server.
- Create a new config file in the
sites-availabledirectory:
sudo nano /etc/apache2/sites-available/direct.conf
Now type the following lines
<VirtualHost *:80>
ServerName xxx.xxx.xxx.xxx
Redirect 403
DocumentRoot /dev/null
</VirtualHost>
- Save the file
- Type
sudo a2ensite direct - Now restart your server:
sudo apache2 restart
Done. You won’t be able to access your website using the IP address of your server.
If you want to disable this particular site configuration, just type sudo a2dissite direct and restart the server (sudo apache2 restart)
EDIT:
You might have to use
Redirect 403 /
As pointed out by Chris (thanks for letting me know).
For me this didn’t work: Redirect 403
It must be: Redirect 403 /
Yeh… Thanks, it´s work!
Works for me with Redirect 403 /
Thanks 🙂
It works great, but you can still access the server via https. You’ll get a warning but if you add an exception you’ll still be able to browse. I wasn’t able for the life of me to circumvent this. So this method works on http, but I’m stuck on https.
There’s a discussion about this on stack exchange / serverfault – https://serverfault.com/questions/607137/restrict-direct-ip-access-to-website. If you find a solution, please come back here so I’ll update the article 🙂
Thanks, will do.
For me work this with https:
ServerName xxx.xxx.xxx.xxx
Redirect 403 /
DocumentRoot /dev/null
Doesn’t work for me, I get an Apache error if I try this.