Repository navigation
External storage will prompt for password but always tell you it's the wrong password #53472
Description
This issue have been created to gather the aftermath of a few fixes that seems to work for some but not for all.
Initial regression PR: #50910
References
- [Bug]: Can't authenticate when Nextcloud want to confirm password #51637
- [Bug]: External storage will prompt for password but always tell you it's the wrong password #51919
- fix: Check that user actually can validate password for js #50465 (31, 30 & 29)
- Disable password confirmation not working zorn-v/nextcloud-social-login#494
- https://www.youtube.com/watch?v=Iqog7N9cRNU
Various findings
- First issue was an ldap/oidc issue where the password should NOT have been requested, but the script was not handling this properly. This got fixed by fix: Check that user actually can validate password for js #50465
- Second related issue was that the password was NOT properly forwarded to the backend. It seemed to be an issue on some setups where mod_rewrite and/or mod_env were NOT enabled. This seems to be mandatory or else the AUTH header is empty
- Third issue was a frontend setting saving issue, fixed by fix(external_storage): fix settings save #51320
Yes and exactly thats why we need to track all those (unrelated!) issues separately.
This issue here is already unmaintainable the discussion is cut by GitHub so context gets missing, different problems get mixed thus we can not get the root causes as basically here we are talking about many different reasons.
So this issue "Dialogs always tells your the password is wrong" is now solved and will be available in next maintenance releases of Nextcloud 33 and 32 (due for 26th of March)
We will of cause happily handle all other issues, but keep them separated to allow one to work on their individual root causes.
We have identified following sub issues:
- Local storage cannot be created
- report…
Metadata
Metadata
Type
Projects
- Status
Activity
skjnldsv commentedon Jun 13, 2025
To everyone finding this issue, I locked this for now so I can think of proper ways to gather the right data.
I got pinged from too many places and because the issue initially came from various different context, this is quite messy.
Right now, It seems like LDAP and OIDC is working properly.
If you're logged in as an ldap or oidc user, the password should NOT be asked.
From my current quick thinking, I gathered that most of you keeps entering the password, but it always errors out by stating the entered password is wrong. If that is the case to you, please apply this patch: #53474
Then I will need a screenshot of your network requests.
Before you do anything, open the development tools, there is a tab called
network. Click on it and then the xhr filter. Do the password confirmation and screenshot the network log like this:How to access your development tools (Click to expand)
Chrome
Safari
Firefox
Opera
155 remaining items
adorobis commentedon Mar 12, 2026
@susnux reading the fix it does not seem to refer in any way to the possible root cause that was provided by @iCaotix - or am I not understanding it well? The fix provided seems to only help distinguish reasons for login failure but in reality most of people affected by this problem do not have failed logins.
susnux commentedon Mar 12, 2026
@adorobis it fixes this issue here reported that the password confirmation says "wrong password" instead of properly handle API errors.
Well but this issue is only about the failed login error:
But most replys here are not about that one issue but various other independant issues that need to be tracked individually.
E.g. some had problems with SFTP (fixed by #54048 ), some with local storage and @iCaotix reported things about S3.
All of those might be issues (some were just misconfigurations) but completely unrelated to this issue and thus need to be tracked as individual issues.
yummiweb commentedon Mar 12, 2026
The problem is that this type of error is difficult to describe in a way that prevents it from being misunderstood by other users with different causes. Even support staff misinterpret the error description, and it's particularly difficult to search for reports specifically about this error.
Therefore, confusion inevitably arises.
But if someone on the team finally understands what the described error is really about, then the team could (should) create a separate bug report for it or at least confirm that it has been recognized as a problem—right? Or is the existence of a problem being questioned?
I've been using Nextcloud for several years, and this problem has only been occurring for a few versions now—on multiple (at least four), completely independent installations.
susnux commentedon Mar 12, 2026
Yes and exactly thats why we need to track all those (unrelated!) issues separately.
This issue here is already unmaintainable the discussion is cut by GitHub so context gets missing, different problems get mixed thus we can not get the root causes as basically here we are talking about many different reasons.
So this issue "Dialogs always tells your the password is wrong" is now solved and will be available in next maintenance releases of Nextcloud 33 and 32 (due for 26th of March)
We will of cause happily handle all other issues, but keep them separated to allow one to work on their individual root causes.
We have identified following sub issues:
So I would like to encourage you to wait for the new updates end of the month and if your issues are not resolved please open a specific new issue for your problem.
Thank you for your understanding!
yummiweb commentedon Mar 12, 2026
susnux commentedon Mar 18, 2026
miversen33 commentedon Mar 18, 2026
susnux commentedon Mar 18, 2026