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

Multi-Level Subdomains #45

Open
colinc opened this issue Oct 26, 2020 · 0 comments
Open

Multi-Level Subdomains #45

colinc opened this issue Oct 26, 2020 · 0 comments

Comments

@colinc
Copy link

colinc commented Oct 26, 2020

When attempting to use this component with a custom, multi-level subdomain (for example, api.micro-service.widget.co) the deployment fails with the error "The domain name to be created is not covered by the provided certificate".

It looks like this is coming from:

const wildcardSubDomain = `*.${instance.state.nakedDomain}`;

Because it's looking for the "naked domain", and attaching the wildcard on the first level subdomain, the certificate ends up being issued for widget.co with an addition name for *.widget.co, neither of which are valid for api.micro-service.widget.co.

Perhaps I'm misunderstanding and there's a workaround or setup step I'm missing. However, if not, I can provide a pull request.

@eahefnawy eahefnawy reopened this Jan 28, 2021
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