The following new error/warning is received in the Admin settings after upgrade: Your web server is not properly set up to resolve `.well-known` URLs, failed on: `/.well-known/webfinger` For more details see the documentation ↗. The documentation suggests adding rewrite rules, e.g. <IfModule mod_rewrite.c> RewriteEngine on RewriteRule ^\.well-known/carddav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/caldav /nextcloud/remote.php/dav [R=301,L] RewriteRule ^\.well-known/webfinger /nextcloud/index.php/.well-known/webfinger [R=301,L] RewriteRule ^\.well-known/nodeinfo /nextcloud/index.php/.well-known/nodeinfo [R=301,L] </IfModule> https://docs.nextcloud.com/server/29/admin_manual/issues/general_troubleshoo... However, adding the settings to httpd-local.conf and reloading makes no difference. Note: caldav and carddav are handled in /etc/webapps/nextcloud/.htaccess Why isn't webfinger handled there? This has to be set by the package as modifying the file manually triggers a hash violation on the modified file. (that can be worked around, but it's a hack) Is this something that needs to be raised as a bug? -- David C. Rankin, J.D.,P.E.