Nginx服务无法公网访问求助（Windows环境）

Hey there, I’ve run into this exact issue with Nginx on Windows a handful of times—let’s walk through the most likely fixes step by step:

1. Fix Nginx’s Listen Address (The Most Common Culprit) #

First, check your server block’s listen directive. If it’s set to listen 127.0.0.1:80;, Nginx will only accept connections from your local machine. You need to tell it to listen on all network interfaces:

server {
    # Listen on all IPs for port 80 (HTTP)
    listen 0.0.0.0:80;
    # Uncomment below if using HTTPS
    # listen 0.0.0.0:443 ssl;

    # Your domain name, public IP, and localhost (can list multiple separated by spaces)
    server_name your-domain.com 123.45.67.89 localhost;

    # Path to your HTML files (use forward slashes or escaped backslashes)
    root C:/nginx/html;
    index index.html;

    location / {
        try_files $uri $uri/ =404;
    }

    # Add SSL certificate config here if using HTTPS
}

0.0.0.0 tells Nginx to accept traffic from every network adapter on your Windows machine, not just the local loopback.

2. Unblock Nginx in Windows Firewall #

Windows Firewall blocks incoming connections by default—this is probably stopping external traffic from reaching Nginx. Here’s how to fix it:

• Open Control Panel > Windows Defender Firewall > Advanced Settings
• Go to Inbound Rules > New Rule
• Select Port > Next
• Choose TCP, enter 80 (and 443 if using HTTPS) > Next
• Select Allow the connection > Next
• Check the network profiles you need (usually Domain, Private, Public) > Next
• Name the rule something like "Allow Nginx HTTP" > Finish

To quickly test if the firewall is the issue, temporarily disable it (don’t forget to re-enable later!)—if you can access the site via public IP after that, the firewall was blocking it.

3. Verify Network & Cloud Security Group Rules #

• If your Windows machine is on a home network behind a router, set up port forwarding in your router. Forward external port 80 to your machine’s local IP (e.g., 192.168.1.100) and port 80.
• If you’re using a cloud server (AWS, Azure, etc.), check your cloud provider’s security group settings. Make sure inbound rules allow TCP traffic on port 80 (and 443) from any IP (0.0.0.0/0).

You can test if the port is open externally by running telnet your-public-ip 80 from another device, or using a simple port check via command line.

4. Confirm Domain DNS Resolution #

If you’re using a domain name, make sure it’s pointing to your public IP:

• Open command prompt and run nslookup your-domain.com—the returned IP should match your server’s public IP.
• DNS changes can take 5-30 minutes to propagate, so if you just updated the records, wait a bit before testing again.

5. Reload Nginx & Validate Configuration #

After making any config changes, always reload Nginx to apply them:

1. Open command prompt, navigate to your Nginx installation folder (e.g., cd C:\nginx-1.25.3)
2. Run nginx -t to test for config syntax errors—if you see "test is successful", you’re good to go.
3. Run nginx -s reload to apply the new config without restarting the whole service.

If nginx -t throws errors, fix the syntax issues first (common mistakes include wrong file paths with backslashes—use forward slashes instead, like C:/nginx/html).

内容的提问来源于stack exchange，提问作者matrixebiz