-
Notifications
You must be signed in to change notification settings - Fork 8
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
Multiple Domains #10
Comments
Hmm, that would be nice, but probably not something I'll implement myself... would gladly accept PRs for it! As long as the config for single-domain users is the same, making the extra domains optional. |
https://laravel-news.com/lets-encrypt-wildcard-ssl-certificates-are-here Any luck with this |
We'll have to wait until acme-client gets updated to use the wildcard stuff new in acme 2.0: unixcharles/acme-client#126 |
Okey |
acme-client is updated! Haven't even had time to look yet, but now it's feasible to register wildcards... |
Since this is of interest to me as well then I took a quick look. From a code perspective, the two biggest changes with acme-client 2.0 appear to be a backwards-incompatible change for creating the acme-client as well as to support a set of domains instead of a simple string. I think that these points are more or less straight-forward to resolve with a bit of elbow grease... However, the bigger issue might be that wildcard certificates currently require a DNS challenge, which I think is not trivial to automate as it depends on interfacing with the DNS provider of choice for a given domain. |
Hey there,
Is it currently possible to generate multiple certificates at once?
For example if you use some subdomains or simply want to support the www. prefix.
Thanks in advance.
Greetings,
Angelo
The text was updated successfully, but these errors were encountered: