-
-
Notifications
You must be signed in to change notification settings - Fork 94
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[WIP] let's encrypt heroku integration #360
Comments
point the CNAME to |
please take care of your custom domain DNS settings as seen above
|
yep i do, changed the settings, site seems to be down now 😱 although i haven't checked before the change. |
from my phone, it looks like the *.cologne.rb has no or bad DNS information. I think the root works, but subdomain configuration is broken. the site works fine through cologne.onruby.de |
mh, any idea? https://devcenter.heroku.com/articles/ssl#change-your-dns-for-all-domains-on-your-app dig www.colognerb.de cname +short
colognerb.de.herokudns.com. sounds ok to me |
sorry, i think it must be with the subdomain changing dns is always such a PITA because of the caching and ttls :( |
yea, should have spotted that myself. now it works:tm: |
DNS resolution still often does not work when people just type in colognerb.de (without the
Some browsers will automatically redirect to the www version, but it seems that it does not work for everybody. |
@jhilden AFAIK you either have to setup CNAME flattening which is not supported by all DNS providers, or setup a redirect from the root to www. |
heroku certs do not really cut it here... i decided to handle everything through cloudflare instead. if you want your domain to run with SSL support, please configure
as your external DNS servers. in case you already have a cloudflare setup, just CNAME your domain to with |
cloudflare is ready to go, we just need the domainserver to be properly configured like so #360 (comment) |
in order to support full SSL via heroku, there need to be some changes to the dns setup.
i'm currently checking it out for the onruby.eu domains so that we can use them as a blueprint for all other domains.
The text was updated successfully, but these errors were encountered: