无法通过公网IP:80访问Node.js+Express搭建的网页，求问题排查

Let’s work through why your public IP + port 80 isn’t loading your Node/Express server—since it works perfectly on Heroku, the problem is tied to your local network setup or port forwarding configuration. Here are the most likely culprits and fixes:

1. Privilege Restrictions on Port 80 #

Port 80 is a "privileged port" on most operating systems (Windows, macOS, Linux). Regular user accounts can’t bind processes to this port by default.

• Quick fix: Have your Express server listen on a non-privileged port (like 3000) instead, then update your port forwarding rule to map public port 80 to your local port 3000.
• If you need port 80 locally:
  • On Linux/macOS, run your server with sudo (not ideal for production, but okay for testing) or set capabilities to let Node bind privileged ports:

    sudo setcap 'cap_net_bind_service=+ep' /path/to/your/node/executable
    

  • On Windows, run your terminal/IDE as Administrator before starting the server.

2. Incorrect Port Forwarding Rule Details #

Even if you followed the screenshot, double-check these critical settings:

• Local IP address: Make sure you’re forwarding to your computer’s internal LAN IP (e.g., 192.168.1.100), not 127.0.0.1—the latter points to the router itself, not your server machine.
• Protocol: Ensure the rule includes TCP (HTTP uses TCP exclusively). Some routers default to UDP, which won’t work for web traffic.
• Rule activation: Don’t forget to save the rule in your router settings—many routers require a manual save before changes take effect.

3. Firewall Blocking the Connection #

• Local firewall: Windows Firewall, macOS Firewall, or Linux iptables might be blocking incoming requests to your server’s port.
  • Temporarily disable the firewall to test (re-enable afterward!), or add a specific rule allowing inbound traffic to your local port (3000 or 80).
• ISP-level blocking: Some internet providers block port 80 to prevent users from hosting public servers. Test with an alternative port (like 8080) by updating your port forwarding rule to map public port 8080 to local port 3000. If that works, your ISP is likely restricting port 80.

4. No Real Public IP (CGNAT) #

Many ISPs use Carrier-Grade NAT (CGNAT), which means your "public IP" is shared with other users—you don’t have a unique, routable IP address. Port forwarding won’t work in this case.

• Check: Visit a site like ifconfig.me (run curl ifconfig.me in terminal) to get your public IP, then search for "IP lookup" to see if it’s listed as a CGNAT address.
• Fix: Contact your ISP to request a static public IP, or use a temporary tunneling tool like ngrok to test external access without port forwarding.

5. Express Server Listening on the Wrong Address #

Make sure your server is configured to listen on 0.0.0.0 (all network interfaces) instead of 127.0.0.1 (only local loopback). If it’s only listening on 127.0.0.1, external requests from port forwarding will be rejected.
Your code should look like this:

const express = require('express');
const app = express();

// Your routes here

app.listen(process.env.PORT || 3000, '0.0.0.0', () => {
  console.log('Server running on all interfaces');
});

6. Step-by-Step Testing to Narrow It Down #

1. Test local access: On your server machine, visit http://localhost:3000 to confirm the server works locally.
2. Test LAN access: From another device on the same WiFi (e.g., your phone), visit http://[your-local-IP]:3000. If this fails, fix local firewall or server listening issues first.
3. Test external access: Turn off WiFi on your phone, use cellular data, and visit http://[your-public-IP]:80 (or your alternative port). If this fails, the problem is with port forwarding or ISP restrictions.

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