Home / Nginx / How to Fix Nginx Server Name Not Matching

Nginx

How to Fix Nginx Server Name Not Matching

Resolve Nginx server_name matching issues including wrong virtual host, default server problems, and domain routing failures.

Published: Nov 28, 20258 min readBy FixWikiHub Editorial Team

Abstract illustration for a troubleshooting knowledge base category.

# Nginx Server Name Not Matching

You configure multiple virtual hosts, but requests go to the wrong one. The wrong site loads, SSL certificates mismatch, or all requests hit the default server regardless of domain. Server name matching determines which server block handles a request, and incorrect configuration leads to unexpected routing.

Introduction

This article covers troubleshooting steps and solutions for How to Fix Nginx Server Name Not Matching. The error typically occurs in production environments and can cause service disruptions if not addressed promptly.

Symptoms

Common error messages include:

bash

curl -H "Host: example.com" -I http://your-server/

nginx

add_header X-Server-Name $server_name always;

```nginx server { listen 80; # No server_name - catches ALL requests root /var/www/default; }

server { listen 80; server_name example.com; root /var/www/example; } ```

Common Causes

Configuration misconfiguration
Missing or incorrect credentials
Network connectivity issues
Version compatibility problems
Resource exhaustion or limits
Permission or access denied

Step-by-Step Fix

1.Check logs for specific error messages
2.Verify configuration settings
3.Test network connectivity
4.Review recent changes
5.Apply corrective action
6.Verify the fix

Understanding Server Name Matching

1.Nginx selects server blocks by:
2.Listening address (IP:port)
3.server_name matching against Host header

1.Priority order:
2.Exact match: server_name example.com
3.Wildcard start: server_name *.example.com
4.Wildcard end: server_name example.*
5.Regex match: server_name ~^(.+)\.example\.com$
6.Default server (first or explicitly marked)

Check which server handles requests: ``bash curl -H "Host: example.com" -I http://your-server/

Add diagnostic header: ``nginx add_header X-Server-Name $server_name always;

Common Cause 1: Missing Server Name

Server block has no server_name, becomes default for all requests.

Problematic config: ```nginx server { listen 80; # No server_name - catches ALL requests root /var/www/default; }

server { listen 80; server_name example.com; root /var/www/example; } ```

Requests to other.com go to the first server (no server_name).

Solution: Define server_name for every block: ```nginx server { listen 80 default_server; server_name _; # Catch-all for unmatched hosts root /var/www/default; }

server { listen 80; server_name example.com; root /var/www/example; } ```

Common Cause 2: Wrong Default Server

Default server isn't explicitly set, first server becomes default.

Problematic config: ```nginx server { listen 80; server_name api.example.com; # First server becomes default for port 80 }

server { listen 80; server_name www.example.com; } ```

Requests to unknown domains go to api.example.com server.

Solution: Explicitly set default: ```nginx server { listen 80 default_server; server_name _; return 444; # Drop connection for unknown hosts }

server { listen 80; server_name example.com www.example.com; root /var/www/example; } ```

Common Cause 3: Server Name Mismatch

Host header doesn't match any server_name.

Diagnosis: ```bash # Check Host header sent curl -v http://example.com/ 2>&1 | grep "Host:"

# Check server_name configuration grep "server_name" /etc/nginx/sites-enabled/*

# Test different hosts curl -H "Host: wrong.com" -I http://your-server/ ```

Problem: Subdomain not listed: ``nginx server { listen 80; server_name example.com; # www.example.com not matched }

Solution: Add all domains: ``nginx server { listen 80; server_name example.com www.example.com *.example.com; }

Common Cause 4: Case Sensitivity Issues

Server_name matching is case-insensitive, but Host headers might vary.

This works correctly: ``nginx server_name Example.com; # Matches "example.com", "EXAMPLE.COM", "Example.com"

Nginx normalizes to lowercase for matching.

Regex matching is case-sensitive: ``nginx server_name ~^Example\.com$; # Only matches exact case "Example.com"

Solution: Case-insensitive regex: ``nginx server_name ~^example\.com$; # Lowercase anchor # or server_name ~^(?i)example\.com$; # Case-insensitive flag

Common Cause 5: Port-Specific Defaults

Default server only applies to specific port.

Problematic config: ```nginx server { listen 80 default_server; server_name _; }

server { listen 443; server_name example.com; # No default for 443 - this becomes default for 443 } ```

HTTPS requests to unknown domains go to example.com.

Solution: Set default for each port: ```nginx server { listen 80 default_server; server_name _; return 444; }

server { listen 443 default_server ssl; server_name _; ssl_certificate /etc/nginx/ssl/default.pem; ssl_certificate_key /etc/nginx/ssl/default.key; return 444; }

server { listen 80; listen 443 ssl; server_name example.com www.example.com; ssl_certificate /etc/nginx/ssl/example.com.pem; ssl_certificate_key /etc/nginx/ssl/example.com.key; root /var/www/example; } ```

Common Cause 6: Regex Priority Issues

Regex matches are checked in order of appearance, not specificity.

Problematic config: ```nginx server { listen 80; server_name ~\.example\.com$; # Matches all subdomains }

server { listen 80; server_name ~^www\.example\.com$; # Never matched - regex order } ```

First regex catches www.example.com.

Solution: Order regex by specificity: ```nginx server { listen 80; server_name ~^www\.example\.com$; # Most specific first }

server { listen 80; server_name ~^(.+)\.example\.com$; # Catch other subdomains } ```

Or use exact/wildcard instead of regex: ```nginx server { listen 80; server_name www.example.com; # Exact match has priority }

server { listen 80; server_name *.example.com; # Wildcard for others } ```

Common Cause 7: Wildcard Syntax Errors

Wildcard patterns have specific syntax requirements.

Invalid wildcards: ``nginx server_name www.*.example.com; # Invalid - wildcard only at start/end server_name *www.example.com; # Invalid - wildcard must be first server_name example.*.com; # Invalid - wildcard only at end server_name *.com; # Invalid - too broad (security risk)

Valid wildcards: ``nginx server_name *.example.com; # All subdomains server_name example.*; # example.com, example.net, etc. server_name .example.com; # example.com AND *.example.com

Common Cause 8: Host Header Missing or Empty

Some requests lack Host header (HTTP/1.0, some bots).

Problematic config: ``nginx server { listen 80; server_name example.com; }

HTTP/1.0 requests without Host go to default server.

Solution: Handle empty Host: ```nginx server { listen 80 default_server; server_name _ "";

# Reject requests without Host if ($host = "") { return 444; } }

server { listen 80; server_name example.com; } ```

Common Cause 9: Multiple Servers Same Name

Duplicate server_name in different blocks.

Problematic config: ```nginx # File A server { listen 80; server_name example.com; }

# File B server { listen 80; server_name example.com; # Duplicate } ```

Nginx picks one arbitrarily, may not be the one you expect.

Solution: Remove duplicates or use different ports: ``nginx # Single server for example.com server { listen 80; listen 443 ssl; server_name example.com; }

Diagnosis: ``bash grep -r "server_name example.com" /etc/nginx/sites-enabled/

Verification

1.List all server_names:
2.```bash
3.sudo nginx -T | grep "server_name"
4.`
5.Test Host header routing:
6.```bash
7.curl -H "Host: example.com" -I http://your-server/
8.curl -H "Host: www.example.com" -I http://your-server/
9.curl -H "Host: other.com" -I http://your-server/
10.`
11.Add diagnostic header:
12.```nginx
13.add_header X-Server-Block $server_name always;
14.add_header X-Host-Header $host always;
15.`
16.Check configuration:
17.```bash
18.sudo nginx -t
19.`
20.Watch which server handles requests:
21.```nginx
22.log_format server '$host -> $server_name [$time_local] $request';
23.access_log /var/log/nginx/server-matching.log server;
24.`

Complete Working Configuration

```nginx # Default server - reject unknown hosts server { listen 80 default_server; listen 443 default_server ssl; server_name _;

ssl_certificate /etc/nginx/ssl/default.pem; ssl_certificate_key /etc/nginx/ssl/default.key;

return 444; # Drop connection }

# Main site server { listen 80; listen 443 ssl; server_name example.com www.example.com;

ssl_certificate /etc/nginx/ssl/example.com.pem; ssl_certificate_key /etc/nginx/ssl/example.com.key;

root /var/www/example;

add_header X-Server-Name $server_name; }

# API subdomain server { listen 80; listen 443 ssl; server_name api.example.com;

ssl_certificate /etc/nginx/ssl/example.com.pem; ssl_certificate_key /etc/nginx/ssl/example.com.key;

location / { proxy_pass http://localhost:3000; } }

# Wildcard for other subdomains server { listen 80; listen 443 ssl; server_name *.example.com;

ssl_certificate /etc/nginx/ssl/example.com.pem; ssl_certificate_key /etc/nginx/ssl/example.com.key;

return 301 https://example.com$request_uri; } ```

Verification

Symptom	Cause	Fix
Wrong site loads	Missing server_name	Add server_name to all blocks
Unknown domains work	No default server	Set `default_server` explicitly
Subdomain not matched	Domain not in list	Add to server_name or use wildcard
Regex not matched	Wrong regex order	Put specific regex before general
HTTPS goes to wrong site	No HTTPS default	Set default for port 443
HTTP/1.0 requests fail	No empty Host handler	Handle empty host in default
Arbitrary server picked	Duplicate server_name	Remove duplicates

Server name matching follows a priority order: exact > wildcard > regex > default. Ensure each server block has appropriate server_name and set explicit default servers for each port.

[Nginx troubleshooting: Fix Lambda Permission Denied - Complete ](fix-lambda-permission-denied)
[Nginx web server troubleshooting: Fix Client Max Body Size Large Upload Nginx Issue ](client-max-body-size-large-upload-nginx)
[Fix Apache 502 Proxy Error](fix-apache-502-proxy-error)
[Fix Apache LogLevel Core Debug Configuration](fix-apache-loglevel-core-debug)
[Fix Cloudflare 502 Bad Gateway Error](fix-cloudflare-502-bad-gateway)

Was this guide helpful?

Related search paths

People also search for

If the symptom is close but not identical, these search paths usually surface the right neighboring fixes faster than scrolling the full archive.

Nginx Server Name Not Matching Nginx Server Name Not Matching Nginx Nginx Server Name Not Matching troubleshooting Nginx Server Name Not Matching fix Resolve Nginx server_name matching issues including wrong virtual host, default server problems, and domain routing failures Nginx Resolve Nginx server_name matching issues including wrong virtual host, default server problems, and domain routing failures

Explore Related Topics

Browse Guides from Other Categories

Discover troubleshooting guides from related categories to expand your knowledge.

FAQ

Nginx Troubleshooting FAQs

Common questions about troubleshooting and preventing similar issues

How do I know if this nginx-errors troubleshooting guide applies to my situation?

This guide is designed for nginx-errors issues. If you're experiencing similar symptoms described in the article, follow the step-by-step instructions. Start with the most common causes and work through the diagnostic process.

Is it safe to follow these nginx-errors troubleshooting steps?

Yes, all steps are designed to be safe and non-destructive. We recommend creating backups before making significant changes and testing each step before proceeding to the next.

How long does it typically take to resolve this type of nginx-errors issue?

Most nginx-errors issues can be resolved within 30 minutes to 2 hours, depending on the complexity and root cause. Follow the troubleshooting flow to identify and fix the problem efficiently.

How can I prevent this nginx-errors issue from happening again?

Regular maintenance, monitoring, and following best practices for nginx-errors configuration can help prevent recurrence. Consider implementing automated checks and alerts for early detection.

Written by

FixWikiHub Editorial Team

Our editorial team consists of experienced DevOps engineers, systems administrators, and cloud architects with hands-on experience in production environments across AWS, Azure, GCP, and on-premises infrastructure.

Every guide undergoes technical review for accuracy and is updated when software versions, commands, or best practices change.

Last updated: Nov 28, 2025

About our team

Important Notice

Disclaimer & Safety Guidelines

The troubleshooting steps in this guide are provided for educational and informational purposes. Before applying any changes to production systems:

Test in a staging environment first — Always verify commands and configurations in a non-production environment before deploying to live systems.
Create backups — Ensure you have current backups of databases, configurations, and critical files before making changes.
Understand the impact — Review how each step may affect your specific environment, dependencies, and users.
Consult official documentation — This guide supplements, but does not replace, official vendor documentation and best practices.

FixWikiHub is not responsible for any damages arising from the use of this content. See our Terms of Use for more information.

Resources

Official Documentation & Further Reading

For authoritative information, consult the official documentation for the technologies discussed in this guide. Our troubleshooting content supplements, but does not replace, vendor documentation.

AWS Documentation — Official Amazon Web Services guides and API references
Kubernetes Documentation — Official Kubernetes documentation
Nginx Documentation — Official Nginx web server documentation
Apache Documentation — Official Apache HTTP Server documentation
Docker Documentation — Official Docker container documentation

How to Fix Nginx Server Name Not Matching

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Understanding Server Name Matching

Common Cause 1: Missing Server Name

Common Cause 2: Wrong Default Server

Common Cause 3: Server Name Mismatch

Common Cause 4: Case Sensitivity Issues

Common Cause 5: Port-Specific Defaults

Common Cause 6: Regex Priority Issues

Common Cause 7: Wildcard Syntax Errors

Common Cause 8: Host Header Missing or Empty

Common Cause 9: Multiple Servers Same Name

Verification

Complete Working Configuration

Verification

People also search for

Browse Guides from Other Categories

WordPress

SSL

DNS

Nginx Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading

How to Fix Nginx Server Name Not Matching

Introduction

Symptoms

Common Causes

Step-by-Step Fix

Understanding Server Name Matching

Common Cause 1: Missing Server Name

Common Cause 2: Wrong Default Server

Common Cause 3: Server Name Mismatch

Common Cause 4: Case Sensitivity Issues

Common Cause 5: Port-Specific Defaults

Common Cause 6: Regex Priority Issues

Common Cause 7: Wildcard Syntax Errors

Common Cause 8: Host Header Missing or Empty

Common Cause 9: Multiple Servers Same Name

Verification

Complete Working Configuration

Verification

Related Articles

People also search for

Share this guide

More Nginx Troubleshooting Guides

Browse Guides from Other Categories

Nginx Troubleshooting FAQs

FixWikiHub Editorial Team

Disclaimer & Safety Guidelines

Official Documentation & Further Reading