-
Notifications
You must be signed in to change notification settings - Fork 301
Closed
Description
Nextcloud reports my rewrite are not setup correctly with message:
Your web server is not properly set up to resolve "/.well-known/webfinger".
I am using 24.0.1-apache image together with an nginx ingress controller, thus using provided configuration both in .htaccess file (part of container) and ingress controller configuration which is:
server_tokens off;
proxy_hide_header X-Powered-By;
client_max_body_size 16G;
fastcgi_read_timeout 3600s;
proxy_buffering off;
gzip off;
rewrite ^/.well-known/webfinger /public.php?service=webfinger last;
rewrite ^/.well-known/host-meta /public.php?service=host-meta last;
rewrite ^/.well-known/host-meta.json /public.php?service=host-meta-json;
location = /.well-known/carddav {
return 301 $scheme://$host/remote.php/dav;
}
location = /.well-known/caldav {
return 301 $scheme://$host/remote.php/dav;
}
location = /robots.txt {
allow all;
log_not_found off;
access_log off;
}
location ~ ^/(?:build|tests|config|lib|3rdparty|templates|data)/ {
deny all;
}
location ~ ^/(?:autotest|occ|issue|indie|db_|console) {
deny all;
}
Metadata
Metadata
Assignees
Labels
No labels