nextcloud/all-in-one
1
1
Fork 0
mirror of https://github.com/nextcloud/all-in-one.git synced 2025-01-18 03:17:39 +08:00
Code Issues Projects Releases Packages Wiki Activity

Add a clarifying comment to nginx ssl-lines for a situation with a subdomain and certbot

Browse source 
Signed-off-by: Anton Podlozny <47890723+apodl1@users.noreply.github.com>
This commit is contained in:
Anton Podlozny 2024-02-26 20:14:36 +02:00 committed by GitHub
parent fbf32ebae0
commit 5b44bb5964
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 1 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

1
reverse-proxy.md
View file

@ -357,6 +357,7 @@ server {
proxy_set_header Connection $connection_upgrade;
}
#if running nginx on a subdomain (eg. nextcloud.example.com) of a domain that already has an wildcard ssl certificate from certbot on this machine, the <your-nc-domain> in the below lines should be replaced with just the domain (eg. example.com), not the subdomain. In this case the subdomain should already be secured without additional actions
ssl_certificate /etc/letsencrypt/live/<your-nc-domain>/fullchain.pem; # managed by certbot on host machine
ssl_certificate_key /etc/letsencrypt/live/<your-nc-domain>/privkey.pem; # managed by certbot on host machine