简体   繁体   English

Twilio语音URL-在实施HTTPS(SSL)时提供HTTP状态代码502

[英]Twilio Voice URL - Giving HTTP status code 502 when HTTPS (SSL) is implemented

I have configured SSL for all of my APIs ( Node.js). 我已经为所有API(Node.js)配置了SSL。 Have purchased certs recently from GoDaddy. 最近从GoDaddy购买了证书。 And I verified using openssl command that its using TLSv1 protocol. 并且我使用openssl命令验证了它使用的是TLSv1协议。

But when I set my Twilio number to call to my API ist throwing HTTP status code 502. It does work when I turn off SSL. 但是,当我将Twilio号码设置为呼叫我的API ist并抛出HTTP状态代码502时。当我关闭SSL时,它确实起作用。 So its clearly issue with Twilio calling my HTTPS API. 因此,Twilio调用我的HTTPS API显然是问题。 Error : An attempt to retrieve content from https://api ... returned the HTTP status code 502. 错误:尝试从https:// api ...检索内容返回了HTTP状态代码502。

Can someone please help ? 有人可以帮忙吗?

It seems Twilio priorities ECDHE ciphers. 似乎Twilio优先考虑ECDHE密码。 By default my Node server was using TLS cipher: TLS_RSA_WITH_AES_256_CBC_SHA256. 默认情况下,我的节点服务器使用的是TLS密码:TLS_RSA_WITH_AES_256_CBC_SHA256。 AES256-SHA is a CBC cipher and therefore susceptible to BEAST attacks. AES256-SHA是CBC密码,因此容易受到BEAST攻击。 Do not use it. 不要使用它。 I added list of all ciphers to include and execlue in my node server. 我在节点服务器中添加了要包含和执行的所有密码的列表。 See doc : https://nodejs.org/api/tls.html 参见文档: https : //nodejs.org/api/tls.html

After adding below options to my node server SSL settings Twilio started communication with my https APIs. 在将以下选项添加到我的节点服务器SSL设置之后,Twilio开始与我的https API进行通信。

    ciphers:[       "ECDHE-RSA-AES256-SHA384",
                    "DHE-RSA-AES256-SHA384",
                    "ECDHE-RSA-AES256-SHA256",
                    "DHE-RSA-AES256-SHA256",
                    "ECDHE-RSA-AES128-SHA256",
                    "DHE-RSA-AES128-SHA256",
                    "HIGH",
                    "!aNULL",
                    "!eNULL",
                    "!EXPORT",
                    "!DES",
                    "!RC4",
                    "!MD5",
                    "!PSK",
                    "!SRP",
                    "!CAMELLIA"
            ].join(':'),
    honorCipherOrder: true

before, we had only these ciphers: 以前,我们只有以下密码:

TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384
TLS_RSA_WITH_AES_256_GCM_SHA384
TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_RSA_WITH_AES_128_GCM_SHA256

we added these: 我们添加了以下内容:

TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256
TLS_RSA_WITH_AES_256_CBC_SHA256
TLS_RSA_WITH_AES_128_CBC_SHA256

and twilio can again connect 并且twilio可以再次连接

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

相关问题 将 AWS ELB 和 ACM 用于 https 时,目标组中的 502 错误和不健康的运行状况状态 - 502 error and unhealthy health status in the target group when using AWS ELB and ACM for https 使用https模块而不是http时,nodejs + nginx出现502错误 - nodejs + nginx getting 502 error when using https module instead of http 当我在节点应用程序中使用https localhost url时,使用ngrok获取502 Bad Gateway错误 - Getting 502 Bad Gateway error with ngrok when I use https localhost url in a Node App 谷歌移动友好 url 测试工具给出 502 错误 - Google mobile friendly url testing tool giving 502 error 在 Twilio 语音中将参与者添加到会议时访问被拒绝 - Access Denied when added participant to conference in Twilio Voice Heroku NodeJS http 到 https ssl 强制重定向 - Heroku NodeJS http to https ssl forced redirect Socket IO ssl独立没有http / https服务器 - Socket IO ssl standalone no http/https server Angular + Node.js HTTP和HTTPS(SSL) - Angular + Node.js HTTP & HTTPS (SSL) 将通知系统更改为SSL。(现在在Chrome中使用https时已被阻止,因为使用了http) - Change notification system to SSL.(right now it's blocked when using https in Chrome because using http) Nginx 入口:将参数添加到 url 时为 502 - Nginx ingress: 502 when adding param to url
 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM