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?
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.
<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/*
In the tutorial, make sure to complete the 2nd-to-last paragraph in <b>Step Five—Set Up the Virtual Hosts</b> (i.e. create a symbolic link to the <code>/etc/nginx/sites-enabled/</code> directory, for EACH domain).