nginx: conflicting server name ignored Nginx / Apache Origin: Edge & web server OSI layer 7 · Application Last updated 5 Nov 2026

Nginx: nginx: [warn] conflicting server name "example.com" on 0.0.0.0:80, ignored

Two server blocks listen on the same port with the same server_name; the second is ignored.

Exact message you may see nginx: [warn] conflicting server name "example.com" on 0.0.0.0:80, ignoredconflicting server name ignored nginx[warn] conflicting server name on [::]:443, ignorednginx conflicting server name warning
Explore the map of this error Full error map →
Seen on: Nginx Linux

Meaning

Nginx picks the first matching server block, so requests may serve the wrong site. Search for duplicates (nginx -T | grep server_name), remove or rename the duplicate, and check sites-enabled for old copies or symlinks.

Common causes

  • Same domain defined in two files
  • Old config left enabled (backup copies like example.com.bak)
  • Symlinks duplicating files
  • HTTP and HTTPS blocks mistakenly with the same listen
  • Wildcard overlap

⚡ Quick fix

  1. sudo nginx -T | grep -n server_name and remove duplicates
  2. Delete backup/symlink copies in sites-enabled
  3. Keep one block per name and port

Detailed fix by platform

Linux

  1. ls -l /etc/nginx/sites-enabled /etc/nginx/conf.d

How to diagnose

  1. Names — Duplicates?
  2. Files — Backups included?
  3. Listen — Same port?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Edge & web server. Errors that are often confused with or caused by this one (click to open):

could not build the server_names_hash, you should increase server_names_hash_bucket_size — Nginx: nginx: [emerg] could not build the server_names_hash, you should increase server_names_hash_bucket_size: 64 (Nginx / Apache)could not build the s…nginx: [emerg] open() failed (2: No such file or directory) — Nginx: nginx: [emerg] open() "/etc/nginx/snippets/fastcgi-php.conf" failed (2: No such file or directory) in /etc/nginx/sites-enabled/app:20 (Nginx / Apache)nginx: [emerg] open()…nginx: [emerg] unexpected end of file, expecting ";" or "}" — Nginx: nginx: [emerg] unexpected end of file, expecting ";" or "}" in /etc/nginx/conf.d/site.conf:42 (Nginx / Apache)nginx: [emerg] unexpe…nginx: directive is not terminated by ";" — Nginx: nginx: [emerg] directive "proxy_pass" is not terminated by ";" in /etc/nginx/sites-enabled/app:15 (Nginx / Apache)nginx: directive is n…nginx: duplicate location — Nginx: nginx: [emerg] duplicate location "/" in /etc/nginx/sites-enabled/default:52 (Nginx / Apache)nginx: duplicate loca…no "ssl_certificate" is defined for the "listen ... ssl" directive — Nginx: [emerg] no "ssl_certificate" is defined for the "listen ... ssl" directive in /etc/nginx/sites-enabled/default:3 (SSL / TLS)no "ssl_certificate" …Welcome to nginx! shown instead of my site — Browser: Welcome to nginx! If you see this page, the nginx web server is successfully installed and working (Nginx / Apache)Welcome to nginx! sho…nginx: co…

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.