Thanks for getting in touch. Great question!
I suppose it sort of depends exactly what you're doing! We absolutely love
LetsEncrypt, which is why its integrated into Symbiosis. However, it wouldn't be
appropriate for our infrastructure and everything we do behind the scenes.
For example, we have many different servers, running different parts of our network
which might require an SSL certificate. So you can imaging having tonnes of servers
running different things requiring a new certificate every 3 months, unfortunately
that isn't feasible for us!
However! That might well change when LetsEncrypt starts using issuing wildcard
certificates! If that's not something you have to worry about and are happy for the
server to keep on ticking along every 3 months renewing a LetsEncrypt SSL
certificate, then its a great option.
What exactly are you seeing it fail on in Symbiosis? Something to be wary of, is
that LetsEncrypt needs to be able to navigate to
/.well-known/acme-challenge without any redirects or custom 404 pages.
So its usually best to exempt .well-known/* from your redirects in the .htaccess
Could you paste us the output of the command:
symbioisis-ssl --verbose - replacing with the relevant
If LetsEncrypt certificates aren't your thing, I'd suggest going with a Comodo
Positive SSL certificate. They're needed on a per-domain basis and only apply to
www. and non-www.