I'm following this tutorial and have read these issues but am still getting stuck configuring my purchased ssl certificate correctly. I'm getting hung up after running the command from step 5 in the tutorial referenced above and getting a
! App not found
error form heroku. Here is a list of domains I have setup within heroku (as an aside when I run heroku domains getting a no resource error as well..).
mydomain.herokuapp.com
mydomian.com
secure.mydomain.com
www.mydomian.com
And all of my cnames records with dnsimple are as follows.
mydomian.com points to proxy.herokuapp.com
www.mydomian.com points to proxy.herokuapp.com
secure.mydomain.com points to proxy.herokuapp.com
I have added the heroku ssl add on, my app name in heroku GUI is mydomain, and have followed steps 1-4 in the tutorial above I believe I have the ssl end correctly configured. I'm not sure what I am missing here to get the above error?
Thanks for your attention on this.
For those in similar situation here was the issue-
After reading this post I updated my .git file with the new name I had given the app. Which is why I was receiving the strange no resource found error above.
After this I just followed heroku documentation starting from here https://devcenter.heroku.com/articles/ssl-endpoint#upload-certificates thus deviating from the blog tutorial I referenced above, and everything seems to be configured correctly.
If you're going through the same process RapidSSL, heroku, DNSimple. I highly recommend following the blog tutorial referenced above and picking up on the heroku documentation linked here if you're interested in getting it up and running quickly.
I hope this helps save some time for someone in the future.
Related
I use a free account with custom domain (Card verified) . I was going through ssl certificates and pasted two codes from heroku site to my app. Later I saw console output shows 7$/mo message.
heroku ps:resize web=hobby
This was the command. Did I changed my billing plan or what? If I did how can I undo it.
My console shows
Dyno types-> Type-web size-hobby qty-1 cost-7$/mo
dyno totals->
type-hobby-total 1
I tried attach a screenshot here. it fails. I came here through heroku support link redirecting here. Can someone explain what I did.
To start with I really don't want to pay for hobby dyno on heroku. I am well aware of their ACM process. I am trying to be a little careful with spends as I am testing something.
My current setup is as follows:
Namecheap (domain xyz.com) -> xyz.herokuapp.com (with DNS Name configured correctly)
This is configured correctly and works great for HTTP. I have a task at hand to obtain certifactes from LetsEncrypt (because they are free), and integrated it to app deployed on heroku.
The app is a simple react-app, built using create-react-app. I have followed the steps to obtain a certificate from LetsEncrypt, and the certbot is asking me to place the certificate in this path public/.well-known/acme-challenge/<cert-string>. The content of the file in that path contains the .
The problem I am having is, the route localhost:3000/.well-known/acme-challenge/<cert-string> works well in my dev environment. When I deployed the react app to heroku, the route /.well-known/acme-challenge/<cert-string> is heading to a 304 and I am unable to facilitate the certbot to complete the validation step.
After a few hours of debugging I understood the architecture inside heroku better, and I have understood that this is a heroku buildpack related problem. My current understanding of the issue is as follows:
heroku blocks access to /.well-known/acme-challenge/<cert-string>
and I have to find a way to unblock this ^ .. so that certbot can validate my cert process.
I did some research and understood that there is a way to by-pass the nginx.conf. Is this really possible?
Looking for some guidance here.
Edit1
I have tried some approaches here https://github.com/heroku/heroku-buildpack-php/issues/218 - they did not work well.
I've followed the guide here for SSL to be automatically configured on my site. It does have the certificate when I visit mysite.herokuapp.com. When I go to my real domain, mysite.com, the site is completely reachable but doesn't seem to have the certificate. I'm pointing the DNS entry to the exact result of 'heroku domains'; note that this entry has not changed since I added SSL it seems. It ends in a .herokudns.com not .herokuapp.com or herokussl.com like I've seen in some of the previous answers on Stack Overflow. I assume that Heroku recently changed this requirement for setup.
I've already waited a few hours. I assume I must be doing something wrong, but I think I've followed the guide correctly, and there are so few steps, so I'm at a loss...
As Chris pointed out in the comments, the solution was heroku is doing something which prevents normal redirection of http to https. This post is very helpful for node js:
https://jaketrent.com/post/https-redirect-node-heroku/
This is my first time getting an SSL certificate for my website. I followed this tutorial https://devcenter.heroku.com/articles/automated-certificate-management
heroku certs:auto displays that Status is "Cert issued". I get no errors. I use git push and the website is still not certified. What could I be doing wrong?
Old question, but if anyone else runs into this problem, which I was just battling myself, here was my problem:
When following the Heroku dev center guide on how to point a custom domain to your herokuapp, the guide says, among other things:
"Create a CNAME record to map from www.example.com to example.herokuapp.com or your SSL endpoint if using SSL."
Neither one of these alternatives are, however, the way to go now (SSL endpoint is considered legacy at Heroku). Instead, once you have added your custom domain correctly, simply:
In Heroku CLI, run "heroku certs:auto:enable" to enable ACM.
Point your domain's DNS records at the Heroku DNS target for your custom domain, which you can find by running "heroku domains"
Wait a little.
This should do it.
Good morning,
I am attempting to update my SSL certificate on Heroku but keep on getting a error:
! Bad response from SSL Endpoint provider. Please try again later.
I have gone though the steps to create a bundle multiple times with no luck. From what I can tell this can mean there is an issue with my certificate or that there is an issue with Herokus services. There is mention of the SSL Doctor tool provided by Heroku, but the Github repo says to use the Toolkit but I have not been able to find any documentation on what the command is or how to use it.
I thought about removing my current SSL key but I have been at this for weeks and I don't want SSL to be down for that long.
Anyone experience this before, or know how to use SSL Doctor (or if SSL Doctor will even help).
Thanks in advance!
I ran into the same problem. It turns out - I was using the Heroku gem to handle the operations. All I had to do was uninstall the Heroku gem, and then install the latest toolbelt from Heroku. The worst part about this problem was that it failed silently. :(