Question

我正在开发使用Node.js和express框架连接到Stripe的API。我的API在容器（FROM node:10.1.0中运行，并且我正在使用docker-compose在Ubuntu 16 VM上运行容器：

version: '2.2'

services:
  api:
    image: my-image:latest
    expose:
      - 80

  nginx:
    image: nginx
    ports:
      - "80:80"
      - "443:443"
    links:
      - api
    volumes:
      - ./nginx.conf:/etc/nginx/nginx.conf

，并带有一个nginx.conf文件：

events {
    worker_connections 1024;
}

http {
  server {
    listen 80;

    location / {
      return 301 https://$host$request_uri;
    }
  }

  server {
    listen 443 ssl;

    ssl_certificate     /etc/nginx/ssl/fullchain.pem;
    ssl_certificate_key /etc/nginx/ssl/privkey.pem;
    ssl_protocols TLSv1.3 TLSv1.2 TLSv1.1 TLSv1;
    ssl_ciphers TLS_CHACHA20_POLY1305_SHA256:ECDHE-ECDSA-CHACHA20-POLY1305:ECDHE-RSA-CHACHA20-POLY1305:DHE-RSA-CHACHA20-POLY1305:ECDHE-ECDSA-AES256-GCM-SHA384:ECDHE-ECDSA-AES256-CCM:ECDHE-ECDSA-AES256-CCM8:ECDHE-ECDSA-ARIA256-GCM-SHA384:ECDHE-ECDSA-AES128-GCM-SHA256:ECDHE-ECDSA-AES128-CCM:ECDHE-ECDSA-AES128-CCM8:ECDHE-ECDSA-ARIA128-GCM-SHA256:ECDHE-RSA-AES256-GCM-SHA384:ECDHE-ARIA256-GCM-SHA384:ECDHE-RSA-AES128-GCM-SHA256:ECDHE-ARIA128-GCM-SHA256:DHE-RSA-AES256-GCM-SHA384:DHE-RSA-AES256-CCM:DHE-RSA-AES256-CCM8:DHE-RSA-ARIA256-GCM-SHA384:DHE-RSA-AES128-GCM-SHA256:DHE-RSA-AES128-CCM:DHE-RSA-AES128-CCM8:DHE-RSA-ARIA128-GCM-SHA256:ECDHE-ECDSA-AES256-SHA384;
    ssl_ecdh_curve X25519:secp521r1:secp384r1;
    ssl_prefer_server_ciphers on;

    try_files   $uri $uri/ =404;

    location /api/ {
      proxy_pass        http://api:80/;
      proxy_buffering   off;
      proxy_set_header  Host $host;
      proxy_set_header  X-Real-IP $remote_addr;
    }
  }
}

运行curl -XPOST https://my.server.com/api/webhook --tlsv1.2 --verbose时，我得到一个很好的响应，看起来像TLS 1.2正常工作：

*   Trying 23.100.121.74...
* TCP_NODELAY set
* Connected to my.server.com (23.100.121.74) port 443 (#0)
* ALPN, offering h2
* ALPN, offering http/1.1
* Cipher selection: ALL:!EXPORT:!EXPORT40:!EXPORT56:!aNULL:!LOW:!RC4:@STRENGTH
* successfully set certificate verify locations:
*   CAfile: /etc/ssl/cert.pem
  CApath: none
* TLSv1.2 (OUT), TLS handshake, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Server hello (2):
* TLSv1.2 (IN), TLS handshake, Certificate (11):
* TLSv1.2 (IN), TLS handshake, Server key exchange (12):
* TLSv1.2 (IN), TLS handshake, Server finished (14):
* TLSv1.2 (OUT), TLS handshake, Client key exchange (16):
* TLSv1.2 (OUT), TLS change cipher, Client hello (1):
* TLSv1.2 (OUT), TLS handshake, Finished (20):
* TLSv1.2 (IN), TLS change cipher, Client hello (1):
* TLSv1.2 (IN), TLS handshake, Finished (20):
* SSL connection using TLSv1.2 / ECDHE-RSA-CHACHA20-POLY1305
* ALPN, server accepted to use http/1.1
* Server certificate:
*  subject: OU=Domain Control Validated; CN=*.server.com
*  start date: Sep  7 16:29:45 2018 GMT
*  expire date: Sep  7 16:29:45 2019 GMT
*  subjectAltName: host "my.server.com" matched cert's "*.server.com"
*  issuer: C=US; ST=Arizona; L=Scottsdale; O=GoDaddy.com, Inc.; OU=http://certs.godaddy.com/repository/; CN=Go Daddy Secure Certificate Authority - G2
*  SSL certificate verify ok.
> POST /api/webhook HTTP/1.1
> Host: my.server.com
> User-Agent: curl/7.54.0
> Accept: */*
> 
< HTTP/1.1 400 Bad Request
< Server: nginx/1.15.7
< Date: Fri, 22 Mar 2019 17:50:33 GMT
< Content-Type: application/json; charset=utf-8
< Content-Length: 68
< Connection: keep-alive
< X-Powered-By: Express
< Vary: Origin
< ETag: W/"44-HsiDCuzDBw0t2vb7UevWXjyvmIo"
< 
* Connection #0 to host api.server.com left intact
{"message":"Unable to extract timestamp and signatures from header"}

但是，我在服务器上没有收到任何Webhook（使用ngrok在本地工作），当在Stripe平台上检查Webhook时，我的服务器Webhook试用版出现此错误：

Status Pending (2 tries)
Next retry around 2019/03/22 18:38 (1 attempt left)
Retry history
[2019/03/22 17:08 to https://my.server.com/api/webhook]: (TLS error) ERR
[2019/03/22 17:38 to https://my.server.com/api/webhook]: (TLS error) ERR

我已经在Linux VM上尝试过https://support.stripe.com/questions/how-do-i-upgrade-my-openssl-to-support-tls-1-2，但是没有任何变化。另外https://support.stripe.com/questions/upgrade-your-node-integration-from-tls-1-0-to-tls-1-2告诉我TLS 1.2 is supported，所以不确定哪里出了错

Answer 1

Stripe需要HTTPS Webhook端点的有效TLS证书，并且大多数情况下，当您的站点缺少中间SSL证书时，就会发生这些问题。具体来说，在SSL实验室结果中，您会在“证书路径”部分看到标记为“额外下载”的一项。您可以在这里确认：https://www.ssllabs.com/ssltest/analyze.html

如果您看到此问题，建议您访问证书颁发者（或从其购买证书的经销商），然后重新安装SSL证书，包括其随附的任何CA证书“捆绑包”。如果您对此有疑问，建议您直接与颁发者和Web主机共享SSL Labs的结果，他们可以指导您找到此中间证书并加以解决。

Answer 2

我设法使用https://whatsmychaincert.com/创建丢失的“链”来解决该问题，然后使用以下命令将其添加到从Azure App Service Cerificate获取的证书中：

cat fullchain.pem example.com.chain.crt> example.com.chained.crt

，并在nginx中将if (isNewDatabase) { s_logger.LogDebug($"New database created. Seed data for SeedMode={databaseConfig.SeedMode}"); foreach (var seeder in scope.ServiceProvider.GetServices<IDbSeeder>().OrderBy(seeder => seeder.Priority)) { seeder.Seed(); s_logger.LogDebug($"Seeded {seeder.GetType().Name}"); } // The changes are usually being saved by a unit of work. Here, while starting the application, we will do it on the context itself. context.SaveChanges(); }用作example.com.chained.crt。现在ssllab告诉我链条已经完成，Stripe给了我200成功

Answer 3

如果您在使用 NGINX 代理服务器运行服务器设置时遇到此问题，您可以解决此问题（由于 SSL 链问题），如 Sectigo 这篇出色的博文中所述。

它对如何安装中间证书以解决链问题有很好的分步说明：

https://support.sectigo.com/Com_KnowledgeDetailPage?Id=kA01N000000zFJQ

Stripe TLS 1.2 Webhook问题

3 个答案: