My domain is:
I ran this command:
It produced this output:
Failed authorization procedure
The client lacks sufficient authorization
Detail: Incorrect validation certificate for TLS-SNI-01 challenge.
from 18.104.22.168:443. Received certificate containing
’www.trymarketspace.com, trymarketspace.com, …
My operating system is (include version):
Ubuntu 14.04 (https://devcenter.heroku.com/articles/stack#cedar)
My web server is (include version):
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
I’m using a control panel to manage my site (no, or provide the name and version of the control panel):
I have an existing production site on Heroku using an SSL Endpoint which uses an existing UCC SAN certificate from another vendor for a number of domains, most of which are owned by my clients, and it also uses a wildcard cert from another vendor. I would like to replace both of there with Heroku’s SNI implementation and a Let’sEncrypt cert.
I’m using Sabayon to generate the certificate and install it on Heroku. This process worked successfully on my staging dynos on heroku which didn’t have an SSL Endpoint. However on the production dynos, the Let’s Encrypt request failed both when I tried it through Sabayon (with an EOF error) and with certbot as described above.
One difference I can see between the two farms is that the production one already has a SAN certificate but the staging one did not. There are likely other infrastructure differences on the Heroku side.
I’m able to browse to the production site and successfully see the challenge response at URL /.well-known/acme-challenge/…