Question

nginx conflict between multiple virtual hosts config files

  • Posted on December 11, 2013
  • robertoAsked by roberto

Hi,

I have followed the guide on https://www.digitalocean.com/community/articles/how-to-set-up-nginx-virtual-hosts-server-blocks-on-ubuntu-12-04-lts--3 . For one virtual host, it works correctly. But when I’ve tried to add the 2nd, the new /etc/nginx/sites/available/ config file has not been recognized by nginx (I’m getting the content from the other domain). Somehow, if I remove the config file for the first host I created, the new one starts working. So I suppose there’s a conflict between both.

Both sites-available config files have the same structure:

server { listen 80; ## listen for ipv4; this line is default and implied #listen [::]:80 default_server ipv6only=on; ## listen for ipv6

    root /var/www/mydomain.com/public_html/;
    index index.html index.htm;

    # Make site accessible from http://localhost/
    server_name mydomain.com;

    access_log /var/log/nginx/mydomain.com.access.log;
    error_log /var/log/nginx/mydomain.com.error.log;

}

Any suggestion please?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

<b>“I’m serious, I think I didn’t touch anything”</b> <br> <br>DNS records can take up to 48 hours to propagate through the Internet (even in situations with multiple DNS changes; some records may be available almost immediately, while others take much longer).

It’s weird, it has started working again, and I think I didn’t touch anything. I’ll perform a backup, just in case I don’t touch anything else and stops working once again :-D <br> <br>I’m serious, I think I didn’t touch anything :-/

Thanks Pablo, that seems to be in order - both domains have their respective symbolic links from /etc/nginx/sites-enabled/* to /etc/nginx/sites-available/*