Debian 8.5下Nginx反向代理Node.js Alexa Skill服务故障求助

Hey there, let's work through this problem step by step. It's super common to hit snags when routing Alexa requests through Nginx to a Node.js app, so let's break down the key areas to check:

1. Verify Your Nginx Configuration #

First, let's make sure your Nginx location block is correctly forwarding requests to /alexa-api (and /alexa-api/) to your Node.js app. The trailing slash in proxy_pass is critical here—it changes how Nginx passes the request path to Node.

Example Correct Config #

If your Node.js app is listening on localhost:3000 and expects requests at /alexa-api, use this setup:

server {
    listen 443 ssl;
    server_name www.myWebsite.com;

    # SSL config (Alexa requires valid, trusted SSL certificates)
    ssl_certificate /path/to/fullchain.pem;
    ssl_certificate_key /path/to/privkey.pem;

    # Main site routing (your existing working config)
    location / {
        proxy_pass http://localhost:3000;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
    }

    # Alexa endpoint routing
    location /alexa-api {
        proxy_pass http://localhost:3000/alexa-api;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header X-Forwarded-Proto $scheme;
        # Allow larger request bodies (Alexa sends JSON payloads)
        client_max_body_size 10M;
    }
}

Key Checks: #

• After updating the config, reload Nginx to apply changes:

  sudo service nginx reload
  

• Check Nginx logs for errors or missing requests:

  tail -f /var/log/nginx/access.log /var/log/nginx/error.log
  

  Look for 404, 502, or 403 responses when hitting the /alexa-api endpoint—this will tell you if Nginx is receiving the request and if it's forwarding it correctly.

2. Validate Your Node.js App's Routing #

Next, confirm your Node.js app (e.g., Express) is set up to handle requests at /alexa-api, regardless of trailing slashes.

Example Express Routing: #

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

// Parse JSON payloads (required for Alexa's request format)
app.use(express.json());

// Handle both /alexa-api and /alexa-api/ requests
app.post('/alexa-api', (req, res) => {
    // Your Alexa skill logic here
    console.log('Received Alexa request:', req.body);
    res.status(200).json({ status: 'success' });
});

// Optional: Handle OPTIONS preflight requests (Alexa may send these)
app.options('/alexa-api', (req, res) => {
    res.setHeader('Access-Control-Allow-Origin', '*');
    res.setHeader('Access-Control-Allow-Methods', 'POST, OPTIONS');
    res.setHeader('Access-Control-Allow-Headers', 'Content-Type');
    res.sendStatus(200);
});

app.listen(3000, () => {
    console.log('Node.js app running on port 3000');
});

Key Checks: #

• Check your Node.js app logs to see if requests from Nginx are arriving. If you don't see any logs for /alexa-api, the issue is with Nginx forwarding.
• Ensure your app is parsing JSON payloads—missing express.json() (or equivalent) will break Alexa request handling.

3. Test the Endpoint Directly #

Before blaming Alexa, test the endpoint yourself to rule out connectivity issues:

Use curl to send a mock Alexa request:

curl -X POST https://www.myWebsite.com/alexa-api \
  -H "Content-Type: application/json" \
  -d '{
    "version": "1.0",
    "session": {},
    "request": {}
  }'

What to Look For: #

• A 200 OK response means the endpoint is working—your issue is likely with Alexa's skill configuration.
• A 404 Not Found means either Nginx isn't forwarding the request, or your Node.js app doesn't have the correct route.
• A 502 Bad Gateway means Nginx can't reach your Node.js app (check if the app is running, port is correct, or firewall rules are blocking traffic).

4. Double-Check Alexa Skill Settings #

Finally, confirm your Alexa skill's endpoint configuration matches exactly:

• Ensure you've selected HTTPS as the endpoint type.
• The endpoint URL should be exactly https://www.myWebsite.com/alexa-api (test both with and without a trailing slash if needed).
• Verify your SSL certificate is trusted by Alexa—Debian 8.5 uses an older OpenSSL version, so make sure your certificate uses compatible cipher suites (avoid TLS 1.3 if you're having issues).

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