Heroku: SSL endpoint - subjectAltName does not match www.mydomain.com

I just set up my first application that requires ssl.

This is a RoR application hosted on Heroku.

I have added the Endpoint SSL add-in to my application. I purchased an SSL certificate from DNSimple.

Then these instructions follow - https://devcenter.heroku.com/articles/ssl-certificate to combine 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 to test my certificate seems fine.

I updated my DNS records with CNAME, which points to my endpoint generated by Heroku.

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 was appreciated.

+7
source share
1 answer

There was nothing wrong with setting / config. There was a delay of about 24 hours, then everything worked as expected.

+5
source

All Articles