-
Notifications
You must be signed in to change notification settings - Fork 44
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
Wildcard SSL support #28
Comments
If I'm reading the sources correctly, adding support for wildcard domains might be as simple as adding star as an allowed character in the Manifest at https://github.com/jelastic-jps/lets-encrypt/blob/master/manifest.jps#L63 - this ticket has been open for about a year, so some kind of an acknowledgement that someone reads the issues would be appreciated. :) |
Hello, it fact is not as simple as just add a star, wildcard support requires another challenge type - dns-challenge (instead of http/tls challenges), this type of challenge requires an access to customer DNS server, in that place the automation of the process becomes more complicated in times as different customers use different DNS servers and DNS services, integration is different for all of them. |
While Jelastic doesn't support it by default, is there any way I can manually configure it to do it? |
Hello, for the current stage it is unable to set WildCard SSL. There are need to be done some improvements to be able to use it. The reason of such complexity is additional validation need to be implemented in Let's Encrypt add-on (set an appropriate challenge type, validation for domain's TXT records in DNS services etc) |
Let's Encrypt already offers Wildacard ssl, but this addon does not support it.
https://community.letsencrypt.org/t/acme-v2-and-wildcard-certificate-support-is-live/55579/5
The text was updated successfully, but these errors were encountered: