From f8a6eb8f32c6626cf65753481a332ed8f86bff82 Mon Sep 17 00:00:00 2001 From: NZTim Date: Sat, 21 Dec 2019 06:58:26 +1300 Subject: [PATCH] Apache configuration for Let's Encrypt webroot validation (#9438) --- docs/content/doc/usage/reverse-proxies.en-us.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/content/doc/usage/reverse-proxies.en-us.md b/docs/content/doc/usage/reverse-proxies.en-us.md index 55c8bb9710..0e4d4b71c7 100644 --- a/docs/content/doc/usage/reverse-proxies.en-us.md +++ b/docs/content/doc/usage/reverse-proxies.en-us.md @@ -129,6 +129,8 @@ If you want Apache HTTPD to serve your Gitea instance, you can add the following Note: The following Apache HTTPD mods must be enabled: `proxy`, `proxy_http` +If you wish to use Let's Encrypt with webroot validation, add the line `ProxyPass /.well-known !` before `ProxyPass` to disable proxying these requests to Gitea. + ## Using Apache HTTPD with a sub-path as a reverse proxy In case you already have a site, and you want Gitea to share the domain name, you can setup Apache HTTPD to serve Gitea under a sub-path by adding the following to you Apache HTTPD configuration (usually located at `/etc/apache2/httpd.conf` in Ubuntu):