files in <document-root>/.well-known are shadowed

How to use GitHub

• Please use the 👍 reaction to show that you are affected by the same issue.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Steps to reproduce

1. use nginx as server backend
2. configure nginx for a subdir deployment as described under https://docs.nextcloud.com/server/21/admin_manual/installation/nginx.html
3. try to access files in <document_root>/.well-known
4. get redirected to nextcloud start page

Expected behaviour

the default configuration should discover filles that are stored under <document_root>/.well-known and serve them

Actual behaviour

if it is a directory an error is returned by nextcloud, if it is a file in a subdirectory one is rerouted to the nextcloud start page.

Server configuration

Operating system:
arch linux

Web server:
nginx

Database:
postgress

PHP version:
php 8

Nextcloud version: (see Nextcloud admin page)
21.0.0

Updated from an older Nextcloud/ownCloud or fresh install:
updated from old install

Where did you install Nextcloud from:
arch package repository

Signing status:

No errors have been found.

List of activated apps:

Enabled:
  - accessibility: 1.7.0
  - admin_audit: 1.11.0
  - calendar: 2.1.3
  - cloud_federation_api: 1.4.0
  - comments: 1.11.0
  - contactsinteraction: 1.2.0
  - cookbook: 0.8.3
  - dashboard: 7.1.0
  - dav: 1.17.1
  - event_update_notification: 1.2.0
  - federatedfilesharing: 1.11.0
  - federation: 1.11.0
  - files: 1.16.0
  - files_pdfviewer: 2.1.0
  - files_rightclick: 1.0.0
  - files_sharing: 1.13.1
  - files_trashbin: 1.11.0
  - files_versions: 1.14.0
  - files_videoplayer: 1.10.0
  - firstrunwizard: 2.10.0
  - gpxpod: 4.2.7
  - logreader: 2.6.0
  - lookup_server_connector: 1.9.0
  - nextcloud_announcements: 1.10.0
  - notifications: 2.9.0
  - oauth2: 1.9.0
  - password_policy: 1.11.0
  - photos: 1.3.0
  - previewgenerator: 3.1.1
  - privacy: 1.5.0
  - provisioning_api: 1.11.0
  - recommendations: 1.0.0
  - serverinfo: 1.11.0
  - settings: 1.3.0
  - sharebymail: 1.11.0
  - support: 1.4.0
  - survey_client: 1.9.0
  - systemtags: 1.11.0
  - text: 3.2.0
  - theming: 1.12.0
  - twofactor_backupcodes: 1.10.0
  - updatenotification: 1.11.0
  - user_status: 1.1.1
  - viewer: 1.5.0
  - weather_status: 1.1.0
  - workflowengine: 2.3.0
Disabled:
  - activity
  - announcementcenter
  - bruteforcesettings
  - contacts
  - encryption
  - files_antivirus
  - files_external
  - flowupload
  - suspicious_login
  - timetracker
  - user_ldap
  - whiteboard

Nextcloud configuration:

[config-next.txt](https://github.com/nextcloud/server/files/6096052/config-next.txt)

Are you using external storage, if yes which one:
local

Are you using encryption: no

Are you using an external user-backend, if yes which one:
no

Client configuration

Browser:
mozilla firefox

Operating system:
windows

Logs

n.a.

Start with the nginx subdirectory deployment instructions linked in the issue and compare them with the reported handling of files under <document_root>/.well-known. Reproduce the redirect and directory-error behavior with nginx, then determine whether the documentation needs correction or the issue belongs in the Nextcloud server repository; done means the documented setup serves these files as expected.