node.js (express) 上的 Alexa Skill Server 使用 nginx 作为反向代理 (https) [英] Alexa Skill Server on node.js (express) using nginx as reverse proxy (https)

问题描述

我正在我的 Debian 8.5 64bit 上运行一个 nginx，它用作我的节点应用程序的反向代理.在路由到特殊应用程序之前，每个请求都会通过我的反向代理.因此我使用这个配置:

i am running a nginx on my Debian 8.5 64bit which is used as reverse proxy for my node applications. Each request walks through my reverse proxy before getting routed to the special apps. Therefor i am using this config:

upstream socket_nodes {
  server 127.0.0.1:3000;
  server myUrl.com:3000;
  server MY.ROOTSERVER.IP.ADDRESS:3000;
}
server {
  listen 80 default_server;
  listen [::]:80 default_server;
  server_name myUrl.com;
  return 301 https://$server_name$request_uri;
}

server {
  # SSL configuration
  #
  listen 443 ssl default_server;
  listen [::]:443 ssl default_server;
  include snippets/ssl-my-website.com.conf;
  include snippets/ssl-params.conf; 

  # Self signed certs generated by the ssl-cert package
  # Don't use them in a production server!
  #
  # include snippets/snakeoil.conf;

  # Add index.php to the list if you are using PHP
  index index.html index.htm index.nginx-debian.html;

  server_name www.myWebsite.com;
  root /root/webserver/app/;
    location ~ /.well-known {
            allow all;
    }
  location / {
     proxy_pass http://localhost:8080;
         proxy_http_version 1.1;
         proxy_set_header Upgrade $http_upgrade;
         proxy_set_header Connection 'upgrade';
         proxy_set_header Host $host;
         proxy_cache_bypass $http_upgrade;
  }
    location /alexa-api/ {
     proxy_pass http://localhost:3000;
  }
  location /at_backend/ {
    proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection "upgrade";
        proxy_http_version 1.1;
        proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
        proxy_set_header Host $host;
        proxy_pass http://socket_nodes;
  }


  # pass the PHP scripts to FastCGI server listening on 127.0.0.1:9000
  #
  #location ~ .php$ {
  # include snippets/fastcgi-php.conf;
  #
  # # With php5-cgi alone:
  # fastcgi_pass 127.0.0.1:9000;
  # # With php5-fpm:
  # fastcgi_pass unix:/var/run/php5-fpm.sock;
  #}

  # deny access to .htaccess files, if Apache's document root
  # concurs with nginx's one
  #
  #location ~ /.ht {
  # deny all;
  #}
}

遗憾的是这不起作用.我可以通过 https (https://www.myWebsite.com) 访问我的网站，并且运行良好.

Sadly this is not working. I can reach my website via https (https://www.myWebsite.com) and it works fine.

所以我将 Amazon Developer Console 中我的 alexa 技能的端点更改为:https://www.myWebsite.com/alexa-api(有和没有尾随 /) 但它不起作用.当我在本地使用并通过 ngrok 使其可用时，技能服务器本身就可以工作.我在这里做错了什么?

So i changed the endpoint of my alexa skill in the Amazon Developer Console to: https://www.myWebsite.com/alexa-api (with and without trailing /) but it is not working. The skill server itself worked when i used it locally and made it available via ngrok. What am i doing wrong here?

还有一个 socket.io 服务器在同一个应用程序中运行，可以从互联网访问(服务器记录新客户端连接") - 但我不能在它们之间发出任何事件.socket.io 连接的 HTTP Status Code 是(正确的)101 Switching Protocols.

There is also a socket.io server running in the same app which can be accessed from the internet (the server loggs "new client connected") - but i can not emit any events between them. The HTTP Status Code of the socket.io connection is (correctly) 101 Switching Protocols.

问候

推荐答案

当你有 HTTPS 时，你也应该通过 https 方案

When you have a HTTPS you should also pass https scheme

proxy_pass https://socket_nodes;

这篇关于node.js (express) 上的 Alexa Skill Server 使用 nginx 作为反向代理 (https)的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！