From 48495f41e898498a91a1b3d9e8fa1950e60a12de Mon Sep 17 00:00:00 2001 From: redmatrix Date: Fri, 22 Jan 2016 02:22:27 -0800 Subject: provide mechanism for custom .well-known handlers and static files (e.g. for letsencypt ownership verification). Document that if you create a .well-known directory to validate a letsencrypt cert you need to remove it before installing hubzilla. We probably need a check for this in the install checklist. --- install/INSTALL.txt | 8 ++++++++ 1 file changed, 8 insertions(+) (limited to 'install') diff --git a/install/INSTALL.txt b/install/INSTALL.txt index 78cea638d..22c7ef35f 100644 --- a/install/INSTALL.txt +++ b/install/INSTALL.txt @@ -62,6 +62,14 @@ When communicating with new sites, Hubzilla always attempts connection on the SSL port first, before falling back to a less secure connection. If you do not use SSL, your webserver MUST NOT listen on port 443 at all. +If you use LetsEncrypt to provide certificates and create a file under +.well-known/acme-challenge so that LetsEncrypt can verify your domain ownership, +please remove or rename the .well-known directory as soon as the certificate is +generated. Hubzilla will provide its own handler for ".well-known" services when +it is installed, and an existing directory in this location may prevent some of +these services from working correctly. + + 1. Requirements - Apache with mod-rewrite enabled and "AllowOverride All" so you can use a local .htaccess file. Some folks have successfully used nginx and lighttpd. -- cgit v1.2.3