You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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".
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.
The text was updated successfully, but these errors were encountered:
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:
express/src/utils.js
Line 497 in 77ab7ad
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.
The text was updated successfully, but these errors were encountered: