Skip to content
GitLab
Closed
Issue created by Colan Schwartz@colanOwner2 of 2 checklist items completed2/2 checklist items

Let's Encrypt HTTPS cannot be enabled during site creation

Sites must first be created (Install tasks) without encryption enabled. Then, once the site has been created, encryption can be enabled. This is most likely because the well-known directory isn't set up until after certificate generation. We'll need to switch these around.

Failed to generate Let's Encrypt certificates.
Injecting Let's Encrypt 'well-known' ACME challenge directory '/var/aegir/config/letsencrypt.d/well-known/acme-challenge' into Nginx vhost entry.

Attempting to enable encryption on site creation yields a 403 (Forbidden) by the CA as it can't access the challenge response. This leads to the warning:

Failed to generate Let's Encrypt certificates.

This issue is completely solved by #28 (closed), but it doesn't support all Web servers just yet:

  • Nginx
  • Apache
Edited by Colan Schwartz
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information