logo

pleroma

My custom branche(s) on git.pleroma.social/pleroma/pleroma
commit: 57501defb40955b1edc2552ecf422b48c573aaee
parent: 612ace96de4553df5779da2bd6650342799b4df0
Author: lambda <pleromagit@rogerbraun.net>
Date:   Sun, 10 Feb 2019 14:21:12 +0000

Merge branch 'adapt-nginx-acme-path-to-guide-recommendation' into 'develop'

Recommend the acme-challenge path that is used in the installation guides

See merge request pleroma/pleroma!803

Diffstat:

Minstallation/pleroma.nginx9+++++----
1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/installation/pleroma.nginx b/installation/pleroma.nginx @@ -15,12 +15,13 @@ server { return 301 https://$server_name$request_uri; # Uncomment this if you need to use the 'webroot' method with certbot. Make sure - # that you also create the .well-known/acme-challenge directory structure in pleroma/priv/static and - # that is is accessible by the webserver. You may need to load this file with the ssl - # server block commented out, run certbot to get the certificate, and then uncomment it. + # that the directory exists and that it is accessible by the webserver. If you followed + # the guide, you already ran 'sudo mkdir -p /var/lib/letsencrypt' to create the folder. + # You may need to load this file with the ssl server block commented out, run certbot + # to get the certificate, and then uncomment it. # # location ~ /\.well-known/acme-challenge { - # root <path to install>/pleroma/priv/static/; + # root /var/lib/letsencrypt/.well-known/acme-challenge; # } }