github/reverse-proxy-confs
1
0
Fork 0
mirror of https://github.com/linuxserver/reverse-proxy-confs.git synced 2025-07-06 04:51:33 -07:00
Code Issues Projects Releases Packages Wiki Activity Actions 2

Fixes for NC21 - changes /.well-known block

Browse source 
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
1 changed files with 10 additions and 11 deletions
Download patch file Download diff file Expand all files Collapse all files

19
nextcloud.subfolder.conf.sample
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
# located at /config/www/nextcloud/config/config.php and add the following lines before the ");":
# 'trusted_proxies' => ['swag'],
@ -11,17 +11,16 @@
# 1 => 'your-domain.com',
# ),
# Redirects for DAV clients
location = /.well-known/carddav {
return 301 $scheme://$host/nextcloud/remote.php/dav;
}
location ^~ /.well-known {
# The rules in this block are an adaptation of the rules
# in the Nextcloud `.htaccess` that concern `/.well-known`.
location = /.well-known/caldav {
return 301 $scheme://$host/nextcloud/remote.php/dav;
}
location = /.well-known/carddav { return 301 /nextcloud/remote.php/dav/; }
location = /.well-known/caldav { return 301 /nextcloud/remote.php/dav/; }
location /nextcloud {
return 301 $scheme://$host/nextcloud/;
# Let Nextcloud's API for `/.well-known` URIs handle all other
# requests by passing them to the front-end controller.
return 301 /nextcloud/index.php$request_uri;
}
location ^~ /nextcloud/ {