Fixes for NC21 - changes /.well-known block

Before this change the config results in a warning `Your web server is not properly set up to resolve "/.well-known/webfinger".`
Source of proposed fix: linuxserver/docker-nextcloud#189
https://github.com/linuxserver/docker-nextcloud/issues/189#issuecomment-846376583
This commit is contained in:
Wdavery 2021-07-14 15:00:22 -04:00 committed by GitHub
parent 6435f9d873
commit fca823b1ff
No known key found for this signature in database
GPG key ID: 4AEE18F83AFDEB23

View file

@ -1,4 +1,4 @@
## Version 2021/07/08 ## Version 2021/07/14
# Assuming this container is called "swag", edit your nextcloud container's config # Assuming this container is called "swag", edit your nextcloud container's config
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");": # located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['swag'], # 'trusted_proxies' => ['swag'],
@ -11,18 +11,17 @@
# 1 => 'your-domain.com', # 1 => 'your-domain.com',
# ), # ),
# Redirects for DAV clients location ^~ /.well-known {
location = /.well-known/carddav { # The rules in this block are an adaptation of the rules
return 301 $scheme://$host/nextcloud/remote.php/dav; # in the Nextcloud `.htaccess` that concern `/.well-known`.
}
location = /.well-known/caldav { location = /.well-known/carddav { return 301 /nextcloud/remote.php/dav/; }
return 301 $scheme://$host/nextcloud/remote.php/dav; location = /.well-known/caldav { return 301 /nextcloud/remote.php/dav/; }
}
location /nextcloud { # Let Nextcloud's API for `/.well-known` URIs handle all other
return 301 $scheme://$host/nextcloud/; # requests by passing them to the front-end controller.
} return 301 /nextcloud/index.php$request_uri;
}
location ^~ /nextcloud/ { location ^~ /nextcloud/ {
include /config/nginx/proxy.conf; include /config/nginx/proxy.conf;