Heroku:SSL端点 - subjectAltName与www.mydomain.com不匹配 [英] Heroku: SSL Endpoint - subjectAltName does not match www.mydomain.com

查看:104
本文介绍了Heroku:SSL端点 - subjectAltName与www.mydomain.com不匹配的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述



这是RoR应用,由Heroku托管。



我已将SSL Endpoint加载项添加到我的应用程序中。
我从DNSimple购买了SSL证书。

然后按照这些说明 - https://devcenter.heroku.com/articles/ssl-certificate
连接必要的文件。然后将它们上传到我的服务器。



到目前为止好。



按照这些说明 - https://devcenter.heroku.com/articles/ssl-endpoint#testing-your-certificate
用于测试我的certificat似乎很好。



我使用指向Heroku生成的Endpoint的CNAME更新了DNS记录。

  heroku certs 

给出:

 端点通用名称过期可信
----------- ------------------ -------------------------------- ------ -------------------- -------
< generated_id> .herokussl.com www.mydomain.com ,mydomain.com 2014-04-29 23:25 UTC真

但是当我尝试时:

  curl -v https://www.mydomain.com 

我得到:

  *关于连接()到www.mydomain.com端口443(#0)
*尝试107.20.162.205 ...连接
*连接到www.mydomain.com(107.20.162.205)端口443(#0)
* SSLv3,TLS握手,客户端hello(1):
* SSLv3,TLS握手,Server hello(2):
* SSLv3,TLS握手,CERT(11):
* SSLv3,TLS握手,服务器已完成(14):
* SSLv3,TLS握手,客户端密钥交换(16):
* SSLv3,TLS更改密码,客户端hello(1):
* SSLv3,TLS握手,完成20):
* SSLv3,TLS更改密码,Client hello(1):
* SSLv3,TLS握手,完成(20):
*使用AES256-SHA进行SSL连接
*服务器证书:
* subject:C = US; ST =加利福尼亚; L =旧金山; O = Heroku,Inc. CN = *。herokuapp.com
*开始日期:2011-04-11 00:00:00 GMT
*截止日期:2014-04-15 12:00:00 GMT
* subjectAltName不匹配www.mydomain.com
*关闭连接#0
* SSLv3,TLS警报,客户端hello(1):
* SSL对等证书或SSH远程密钥不正确
curl:(51)SSL对等证书或SSH远程密钥不正确

解决方案

setup / config没有错 - 大概有24小时的延迟,然后一切按预期工作。

I have just been setting up my first app that requires ssl.

It's RoR app, hosted on Heroku.

I have added the SSL Endpoint add-on to my app. I purchased a SSL certificate from DNSimple.

Then followed these instructions - https://devcenter.heroku.com/articles/ssl-certificate to concatenate the necessary files. Then uploaded them to my server.

So far so good.

Following these instructions - https://devcenter.heroku.com/articles/ssl-endpoint#testing-your-certificate for testing my certificat seems fine.

I have updated my DNS records with a CNAME that points to my Heroku generated Endpoint.

heroku certs

gives:

Endpoint                      Common Name(s)                          Expires               Trusted
----------------------------  --------------------------------------  --------------------  -------
<generated_id>.herokussl.com  www.mydomain.com, mydomain.com          2014-04-29 23:25 UTC  True

But when I try:

curl -v https://www.mydomain.com

I get:

* About to connect() to www.mydomain.com port 443 (#0)
*   Trying 107.20.162.205... connected
* Connected to www.mydomain.com (107.20.162.205) port 443 (#0)
* SSLv3, TLS handshake, Client hello (1):
* SSLv3, TLS handshake, Server hello (2):
* SSLv3, TLS handshake, CERT (11):
* SSLv3, TLS handshake, Server finished (14):
* SSLv3, TLS handshake, Client key exchange (16):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSLv3, TLS change cipher, Client hello (1):
* SSLv3, TLS handshake, Finished (20):
* SSL connection using AES256-SHA
* Server certificate:
*    subject: C=US; ST=California; L=San Francisco; O=Heroku, Inc.; CN=*.herokuapp.com
*    start date: 2011-04-11 00:00:00 GMT
*    expire date: 2014-04-15 12:00:00 GMT
*    subjectAltName does not match www.mydomain.com
* Closing connection #0
* SSLv3, TLS alert, Client hello (1):
* SSL peer certificate or SSH remote key was not OK
curl: (51) SSL peer certificate or SSH remote key was not OK

Any help appreciated.

解决方案

There was nothing wrong with the setup/config - There was a delay of about 24hrs, then everything worked as expected.

这篇关于Heroku:SSL端点 - subjectAltName与www.mydomain.com不匹配的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆