如何从局域网外部访问我用Node.js与Express搭建的WebService？

Hey there! Let's get your Express service accessible from outside your local network—here's a clear, step-by-step breakdown of what you need to do:

First, you need to know your router's external (public) IP address—this is the address devices outside your local network will use to reach your service. You can:

• Open a terminal and run curl ifconfig.me (works on Linux/macOS/Windows with Git Bash)
• Or just search "what's my IP" in a browser on any device connected to your network.
  Note: This is different from your local 192.168.0.xxx address—don't mix them up!

This is the critical step that routes external traffic to your local server. The exact steps vary by router brand (like TP-Link, Asus, Netgear), but here's the general process:

• Log into your router's admin panel (usually at 192.168.1.1 or 192.168.0.1—check the label on your router for the exact address and login credentials).
• Look for a section called Port Forwarding, Virtual Servers, or NAT Rules.
• Create a new forwarding rule with these details:
  • External Port: 8080 (or a different port if you prefer—just make sure it matches what you use later)
  • Internal IP Address: The local IP of your server (the 192.168.0.xxx you use to access it on the LAN)
  • Internal Port: 8080 (must match the port your Express app is listening on)
  • Protocol: Select TCP (or TCP+UDP if you need it for other features)
• Save the rule and restart your router if prompted.

By default, some Express apps listen only on localhost (which means they won't respond to external requests). Make sure your app is set to listen on 0.0.0.0—this tells it to accept connections from all network interfaces. Here's how your code should look:

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

// Add your routes and middleware here
app.get('/', (req, res) => {
  res.send('Hello from outside the LAN!');
});

// Listen on all interfaces, port 8080
app.listen(8080, '0.0.0.0', () => {
  console.log('Server running and ready for external connections!');
});

Firewalls (both on your server and sometimes your ISP) can block incoming traffic:

• Local Firewall: On the computer running your Express app, make sure port 8080 is allowed for incoming connections.
  • Windows: Go to Windows Defender Firewall → Advanced Settings → Inbound Rules → New Rule, then allow port 8080.
  • Linux: Run sudo ufw allow 8080/tcp (if using UFW) or adjust your iptables rules.
  • macOS: Go to System Settings → Network → Firewall → Options, then add an exception for your Node.js process or port 8080.
• ISP Firewall: Some ISPs block common ports like 80 or 443. If 8080 doesn't work, try a less common port (like 3001 or 8081) and update your port forwarding rule to match.

Now, disconnect from your local WiFi and use mobile data (or a different network outside your LAN). Open a browser and visit http://[your-public-ip]:8080—you should see your Express service's response!

If your ISP assigns you a dynamic IP (it changes when you restart your router), you can use a Dynamic DNS (DDNS) service to map a fixed domain name to your changing IP. Most routers have built-in support for services like No-IP or DuckDNS:

• Sign up for a free DDNS account to get a domain (e.g., myexpressservice.duckdns.org).
• Configure your router's DDNS settings with your account details.
• Now anyone can access your service using http://your-ddns-domain:8080 without needing to track your changing IP.

内容的提问来源于stack exchange，提问作者Andrés