Erro inesperado: Invalid response: 401

[Everton_Diego_Silva]

Hello,

I am experiencing a persistent “Invalid response: 401” error when navigating through folders in the Files app. This error appears intermittently, and a page refresh (F5) temporarily fixes it, but it always comes back. I have tried every standard configuration fix and the problem persists.

My Environment:

• Nextcloud Version: 31.0.7.1
• Installation: Docker (managed with Portainer)
• Services: nextcloud:latest, mariadb:10.6, redis:alpine, jc21/nginx-proxy-manager:latest
• PHP Version: 8.3.23

My config.php is correctly configured:
(Aqui, cole o seu ficheiro config.php completo, como o que eu lhe enviei na nossa conversa anterior. Lembre-se de esconder a sua dbpassword, secret e passwordsalt).

What I have already tried without success:

• Configured Redis for session handling, local cache, and file locking.
• Corrected trusted_proxies to the specific internal IP of the reverse proxy container (172.20.0.2).
• Corrected all overwrite parameters (overwriteprotocol, overwritehost).
• Removed the overwritecondstr parameter.
• Synced the server’s host clock using NTP.
• Restarted all Docker containers multiple times.
• Cleared the server-side cache with occ maintenance:repair.
• Cleared browser cache completely and tested in an incognito window (the problem persists).
• As a diagnostic test, I disabled Redis session handling, and the 401 error still occurred.

Logs:
The Nextcloud log shows successful requests, followed by a PROPFIND request that gets a 401 response. The Nginx Proxy Manager log does not show any errors.

Example of the failing request from Nextcloud’s log:
181.191.46.243 - - [21/Jul/2025:05:46:21 +0000] "PROPFIND /remote.php/dav/files/evertondiego.dev%40gmail.com/CONTABILIDADE%20-%202025/ HTTP/1.1" 401 922 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/138.0.0.0 Safari/537.36"

Given all these steps, I believe this might be a bug. Can anyone provide further insight? Thank you.