I’m the main developer of Own-Mailbox, a small self-hosted, privacy-protecting, plug and play, e-mail server. (see www.own-mailbox.com ).
We would like to thank you for listing our project here: https://letsencrypt.org/docs/client-options/
We are releasing an alpha testing version in one week. If people from Let’s encrypt would like to test it it would be with great pleasure.
Unfortunately we just discovered a major problem related to the use of Let’s encrypt within the Own-Mailbox project: the number of certificate that Let’s encrypt accepts to issue for sub-domains of .omb.one is limited. And we are giving these sub-domains to our users, that use them as their main domain. This means only a small fraction of them will be able to generate certificates, for their HTTPs server
Could you give the exact limitation. How exactly does let’s encrypt determine
whether too many certificates were issued or not?
This problem really is a shame:
1)Because until we discovered this problem Own-Mailbox configuration was almost magical of simplicity, and having the webmail accessible in the browser, with a correct certificate, after a very simple configuration process was so great!
2)Because soon I may have hundreds, or even thousands users, that will be hosting an https server, in self-signed mode… (Which I think Let’s encrypt wanted to eradicate)
3)It actually makes its impossible to self-hosting a proper HTTPS with certificate for free AND in an automatic/user-friendly way. Because people will have to pay for a Top Level Domain and mess with TLD resellers.
I don’t know to what extend I can dream that this problem can be over-come in the future.
Thanks in advance for your answers,