Python脚本监听TCP 443端口无法接收外部请求，求助技术支援

Hey Rodrigo, sorry to hear you’ve spent hours digging into this without luck—let’s walk through the most likely issues that would block external requests while letting local ones work:

1. Check Your Listener’s Bind Address #

This is the #1 culprit for "local only" access. If your Python script is binding to 127.0.0.1 (localhost) instead of 0.0.0.0, it will only accept connections from the server itself.

Look for code like this in your script:

# Wrong - restricts to local access only
server_socket.bind(('127.0.0.1', 443))

# Correct - accepts connections from any network interface
server_socket.bind(('0.0.0.0', 443))

If you’re using a web framework (like Flask, FastAPI), make sure you set the host parameter properly:

# Flask example with HTTPS
app.run(host='0.0.0.0', port=443, ssl_context=('cert.pem', 'key.pem'))

# FastAPI example with HTTPS
uvicorn.run(app, host='0.0.0.0', port=443, ssl_keyfile='key.pem', ssl_certfile='cert.pem')

2. Verify Firewall & Security Group Rules #

Even if your script is listening correctly, firewalls can block incoming traffic on port 443:

• Server local firewall: Use these commands to check if port 443 is open for inbound traffic:

  # For ufw (Ubuntu/Debian)
  ufw status
  
  # For iptables
  iptables -L -n | grep 443
  

  If you don’t see an allow rule, add one:

  ufw allow 443/tcp
  

• Cloud provider security group: If your server is on AWS, GCP, Azure, etc., you need to explicitly add an inbound rule allowing TCP port 443 from your external IP (or 0.0.0.0/0 for testing purposes).

3. Check for Port Forwarding/NAT Issues #

If your server is on a local network (behind a router), external requests won’t reach it unless you set up port forwarding on your router. You’ll need to map the router’s public port 443 to your server’s private IP and port 443.

4. Validate HTTPS Certificate Configuration #

Since you’re using HTTPS, external clients (like Postman) might reject self-signed certificates, causing silent failures:

• In Postman, go to Settings > General and toggle off "SSL certificate verification" to test if this is the issue.
• If that works, consider using a trusted certificate (Let’s Encrypt is free) or distributing your self-signed certificate to clients.

5. Check for Port Conflicts #

Make sure no other service (like Nginx, Apache, or another process) is already listening on port 443. Run this command to see which process is using the port:

ss -tulpn | grep 443

If another process is bound to 443, you’ll need to stop it or change your script to use a different port (though 443 is standard for HTTPS).

Start with the first two checks—bind address and firewall—since those are the most common fixes for this exact scenario. Let me know if any of these lead you to a solution!

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