Nginx with a domain and subdomain

Posted December 31, 2017 88.4k views
NginxUbuntu 16.04

Hi guys,

First timer configuring nginx here, hope you can help me.

I have my domain, let’s say And I have my app, which I would like to run on will be running a behind a wordpress web server and will be running behind a nodejs server.

So this is my ngnix config file:

server {
        listen 80;
        root /var/www/html;

        # Add index.php to the list if you are using PHP
        index index.html index.htm index.nginx-debian.html;


        location / {
                # First attempt to serve request as file, then
                # as directory, then fall back to displaying a 404.
                try_files $uri $uri/ =404;

server {
        listen 80;

        location / {
                proxy_pass http://localhost:3000;
                proxy_set_header Host $host;
                proxy_set_header X-Real-IP $remote_addr;
                proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
                proxy_connect_timeout 150;
                proxy_send_timeout 100;
                proxy_read_timeout 100;
                proxy_buffers 4 32k;
                client_max_body_size 8m;
                client_body_buffer_size 128k;

when I run ngnix -t I get:

<^>root@ubuntu-1gb-sgp1-01:/etc/nginx/conf.d# nginx -t
nginx: [warn] conflicting server name “” on, ignored
nginx: the configuration file /etc/nginx/nginx.conf syntax is ok
nginx: configuration file /etc/nginx/nginx.conf test is successful<^>

What am I doing wrong?

Thank you

1 comment
  • You probably just disvered as I did recently, that no matter what the nginx documentation says, they too have no clue to differenciate “plain” domain names from prefixed (subdomain) domains.

    nginx evaluates:

    as true for any combination of the above.

    And no. two server names in a block is NOT an nginx error.

    The second block “” will be triggered at the first block “” since the latter means “*”

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.

Submit an Answer
2 answers

Hi @fcaldas

In your first server block, you have two server_name entries which is causing the warning. Please try removing:


Once removed from the first server block, please try testing the configuration once again.

Ignore me, guys… I noticed my error. Sorry about that :)
Happy NYE!