Heroku自定义域名SSL警告 [英] Heroku Custom Domain SSL Warning
问题描述
我正在尝试为Heroku Deployed应用程序设置GoDaddy购买的自定义域。我得到它的工作，以便www。 _ .com正确地转发到我的herokuapp（雪松），但是1）我尝试获取裸地址不起作用，并且2）当我尝试第一次登录到自定义域，我得到了这个警告的浏览器依赖版本，我绝对不想这样做：
这可能不是您要查找的网站！...您应该
可能无法继续......在这种情况下，
证书中列出的地址与您的浏览器
试图去的网站，其中一个可能的原因是您的
通信被攻击者拦截，该攻击者为另一个网站提供
a证书，这会导致不匹配。
另一个可能的原因是服务器设置为返回多个网站的
相同证书，包括您尝试访问的
相同的证书，即使该证书不适用于所有
的网站。谷歌浏览器可以肯定地说你已达到
* .herokuapp.com，但无法验证这是你想要达到的网站。如果您继续操作，Chrome
将不会检查是否有任何其他名称不匹配。
跨越自定义地址之前的HTTPS显然，我不想用这个警告来吓唬游客，但我也不想通过GoDaddy购买SSL证书。我并不需要SSL加密。任何想法如何转发裸体网站，并得到这个工作，而不吓跑访问者？
谢谢，我知道这是一个模糊的问题，而不是Stack Overflow的专业，但我已经捕获围绕谷歌/ Heroku的帮助/ GoDaddy，并发现很少的最新信息，可以帮助我排序通过所有这些。
Sasha
您是否将流量从您的域名转发到yourapp.herokuapp.com？
从您的网站不确定问题是否完全理解转发和使用自己的域名服务器（DNS）之间的区别。
我猜您得到https错误的原因是因为您转发到https。
我会使用zerigo附加组件，它确实简化了一切。您不必使用转发功能，而是将您的域名指向Zerigo的DNS。
https://devcenter.heroku.com/articles/zerigo_dns
I'm trying to set up a GoDaddy-purchased custom domain for my Heroku Deployed app. I got it to work so that the www._.com forwards correctly to my herokuapp (cedar), but 1) my attempts to get the naked address haven't worked, and 2) when I attempt to log on to the custom domain for the first time, I get a browser-dependent version of this warning, which I definitely don't want:
"This is probably not the site you are looking for! ... You should probably not proceed... In this case, the address listed in the certificate does not match the address of the website your browser tried to go to. One possible reason for this is that your communications are being intercepted by an attacker who is presenting a certificate for a different website, which would cause a mismatch. Another possible reason is that the server is set up to return the same certificate for multiple websites, including the one you are attempting to visit, even though that certificate is not valid for all of those websites. Google Chrome can say for sure that you reached *.herokuapp.com, but cannot verify that that is the same site as which you intended to reach. If you proceed, Chrome will not check for any further name mismatches."
The HTTPS before the custom address is crossed out in red. Obviously, I don't want to scare visitors away with this warning, but I also don't want to have to buy an SSL certificate through GoDaddy. I don't really need SSL encryption. Any idea how to forward the naked site and get this to work without scaring off visitors?
Thanks. I know this is a sort of vague question and not Stack Overflow's specialty, but I've fished around google/Heroku help/GoDaddy and found very little up-to-date info that could help me sort through all this.
Sasha
Are you forwarding traffic from your domain to yourapp.herokuapp.com?
Not sure from your question if you fully understand the difference between forwarding and using your own name servers (DNS).
I'm guessing the reason your getting the https error is because you're forwarding to https.
I'd use the zerigo add-on, it really simplifies everything. Instead of using forwarding, you'd point your domain to Zerigo's DNS.
https://devcenter.heroku.com/articles/zerigo_dns
这篇关于Heroku自定义域名SSL警告的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
