Heroku Custom Domain Protection Warning

Question

I am trying to configure the GoDaddy purchased custom domain for my Heroku Deployed application. I got it to work so that www._.com correctly switched to my herokup (cedar), but 1) my attempts to get a bare address did not work and 2) when I try to enter the user domain for the first time I get a browser dependent version of this warning, which I definitely don't want:

"Perhaps this is not the site you are looking for! ... probably will not go on ... In this case, the address indicated in the certificate does not match the address of the website of your browser tried to go. One of the possible reasons for this is that communication is intercepted an attacker who is submitting a certificate for another website, which could lead to inconsistencies Another possible reason is that the server is configured to return the same certificate for several websites, including the one you are trying to visit, although this certificate It’s not valid for all of these websites. Google Chrome can say for sure that you have reached * .herokuapp.com, but cannot verify that it is the same site that you are going to link to. If you continue, Chrome will not check if there are any further name mismatches. "

HTTPS before the user address is crossed out in red. Obviously, I do not want to scare visitors with this warning, but I also do not want to buy an SSL certificate through GoDaddy. I do not need SSL encryption. Any idea how to direct a bare site and make it work without scaring away visitors?

Thanks. I know this is a kind of vague question, not Stack Overflow's specialty, but I was hunting for google / Heroku / GoDaddy for help and found very little relevant information that could help me figure this out.

Sasha

Answer 1

Do you forward traffic from your domain to yourapp.herokuapp.com?

Not sure about your question if you fully understand the difference between forwarding and using your own name servers (DNS).

I assume the reason for getting the https error is because you are forwarding https.

I would use the zerigo supplement, it really simplified everything. Instead of using forwarding, you should specify your domain in Zerigo DNS.

https://devcenter.heroku.com/articles/zerigo_dns

Answer 2

Thanks mc6688. I tried zerigo . I need my application to be accessible from the root domain, as well as from a subdomain like www . And Zeri decides that.

However, Sasha’s problem is not related to DNS, but to SSL. There are two ways to solve this problem, depending on your needs:

• If you use http , then your environments/production.rb application should have the following configuration config.force_ssl = false , which is true by default. Change it to false. If Firefox is still complaining, then reset it. Other browsers should be fine.

• But if you need https , then you should use your own (and not the hero) certificate through an SSL addon, which is a paid service.