Skip to content
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

Help: Deployed, configured, ran, works, except for bindings #24

Open
JoshuaCarroll opened this issue Nov 5, 2020 · 1 comment
Open

Comments

@JoshuaCarroll
Copy link

I was able to use this in our environment, and it issued a certificate for *.arkansasrepeatercouncil.org but it is only bound to https://www.arkansasrepeatercouncil.org and not https://arkansasrepeatercouncil.org.

When I open the TLS/SSL settings on the app service for the site, it lists "www.arkansasrepeatercouncil.org" with a certificate. But if I attempt to add a new binding for "arkansasrepeatercouncil.org" it says "No certificates match the selected custom domain". Thoughts?

@ohadschn
Copy link

ohadschn commented Nov 6, 2020

Root domain (foo.com) is not included in wildcard, duplicate of #8 (you can probably close this issue).

You'd need to set the root domain to a different certificate. You can either use @sjkp's original https://github.com/sjkp/letsencrypt-siteextension, or if you prefer the "external" (no extension) approach taken by this project you can use my variant based on the former: https://github.com/ohadschn/letsencrypt-webapp-renewer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants