Daan Raatjes

It currently does not support SubjectAlternativeNames but this should be rather easy to implement. I can probably release this in a couple of days.

Feature added to [v0.5.0](https://github.com/Daanra/laravel-lets-encrypt/releases/tag/v.0.5.0)

Thanks for the effort! I think it can be done without breaking changes by adding the SAN functionality to the `PendingCertificate` class. For example: ```php LetsEncrypt::certificate('mydomain.com') ->subjectAlternativeNames(['mydomain2.com']) ->create(); ```

@Muffinman Thanks, looks great!

This seems like a good feature to have. > Kindly let me know whether I should send a PR or you can manage it. Would be great if you could...

I agree with you that this feature would be great. But as you said, to make this work automatically, we'd need different implementations for the DNS providers. I have considered...

Issues with Postgres now: https://github.com/Daanra/laravel-lets-encrypt/pull/31#issuecomment-1487985386

Did you see this part from the README? > Note: > > You somehow have to return a stored challenge whenever it it retrieved from the /.well-known/acme-challenge endpoint. You could...