Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I added ip-based virtual host to sites-availble and created symlink to sites-enabled, but new domain times out.

When i navigate to it says connection timed out.

        ServerAdmin webmaster@localhost

        DocumentRoot /var/www/
        <Directory />
                Options FollowSymLinks
                AllowOverride None
        <Directory /var/www/>
                Options Indexes FollowSymLinks MultiViews
                AllowOverride None
                Order allow,deny
                allow from all

        ScriptAlias /cgi-bin/ /usr/lib/cgi-bin/
        <Directory "/usr/lib/cgi-bin">
                AllowOverride None
                Options +ExecCGI -MultiViews +SymLinksIfOwnerMatch
                Order allow,deny
                Allow from all

        ErrorLog /var/log/apache2/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn

        CustomLog /var/log/apache2/access.log combined
        ServerSignature On

    Alias /doc/ "/usr/share/doc/"
    <Directory "/usr/share/doc/">
        Options Indexes MultiViews FollowSymLinks
        AllowOverride None
        Order deny,allow
        Deny from all
        Allow from ::1/128

share|improve this question

Did you add to your server as a secondary address to one of its network interfaces? On Debian/Ubuntu, you would need to add lines like the following to your /etc/network/interfaces file (making an assumption about the netmask):

auto eth0:12
iface eth0:12 inet static

And then run ifup eth0:12 as root.

share|improve this answer
And add the port at the end of the IP address in apache configuration like: NameVirtualHost and <VirtualHost> – Mircea Vutcovici Mar 22 '10 at 3:49

By navigate to I'm going to assume you actual mean which is what is mentioned in your example configuration.

1: That being said, make sure actually set in DNS to resolve to and that the change has propagated through DNS. 2: Make sure to completely restart apache to make sure it picks up the new configuration. Do a restart or even better a stop then start.

Do you see any activity from your client's IP in the access log?

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.