Keepass2android: Nextcloud (and webdav sync) not working with non-ascii characters in password

[lindhe]

I'm not 100% sure it's your fault—it could be something broken on my Nextcloud installation—but since I didn't have any problems before upgrading to the beta version on Google Play, it feels like it's caused by the app.

I can not add a Nextcloud (or Nextcloud-hosted https/webdav) account to sync a database file. I'm just presented with the following error every time:

I'll add logs shortly. But today I'm too tired to trust myself to properly vet the log from plaintext passwords.

EDIT: Adding the text so that it can be indexed better in search engines.

Error Cannot connect to file provider service Received unexpected response: Response{protocol=http/1.1, code=401, message=Unauthorized, url=https://nextcloud.lindhe.io/remote.php/webdav}

[firesoft-de]

Same here, except protocoll=h2

[ouzowtf]

Webdav works for me. After several testing I found out that I have to use the full username (complete email address) for the login, instead of the short one (without @domain.tld).
I don't know if this was the exact same error message, but it was a similar type.

[lindhe]

I tried to produce some logs today, but I literally couldn't. Nothing happens when I press the "Send debug log..." button. Is that the case for you guys?

I tried reinstalling the app and restart the phone, but with no avail. If anyone else is having this problem with the logs, we'll probably need to hunt that one down first.

[lindhe]

286 is definitely the same issue. Sorry for missing it when opening this ticket. I'll leave this alive, just to make it easier to find when searching.

[serioustk]

I encountered the same issue today.
The problem was that I had a german umlaut in my password. I removed the affected character and everything worked out well.
Hope this helps someone.

[lindhe]

Interesting. Yeah, the same for me. When going only with ASCII characters, it works. Might there be a missing encoding to URL format? It seems like the password is passed in a variable called httpPath, that's why the thought struck me...

https://github.com/PhilippC/keepass2android/blob/ef8b9b06854e1fc68a4510b7f130e9d835c371ef/src/keepass2android/FileSelectHelper.cs#L273-L275

[dbielz]

Maybe something different? See #747 , I have no Umlauts in my password.

[firesoft-de]

I can confirm @serioustk, thanks btw
In my case the problem was also related to non ascii / unicode chars in the password. I was able to bypass the problem by using an "app-password" generated via nextcloud user menu Settings / Security / Devices&Session / Generate new app password.
These passwords don't contain any unicode chars and you don't have to change the main password for your account.

Had the exact same problem with the desktop version of keepass. Are there any libraries which are used by both android and pc?

[siegmund42]

Today it happened to me as well, getting a 401 as long as I have a German umlaut (non-ASCII) in my password. If I remove it, everything is just fine..
I'm not very deep into the topic, but the cause seems to be an encoding mismatch between nextcloud server and your client, see https://github.com/owncloud/core/issues/7894 for explanation.
So could you please try a UTF8 encoding in the client?

[siegmund42]

I was able to bypass the problem by using an "app-password" generated via nextcloud user menu Settings / Security / Devices&Session / Generate new app password.
These passwords don't contain any unicode chars and you don't have to change the main password for your account.

@firesoft-de Thanks for this nice workaround, by the way!

[PhilippC]

I just tested this with an account on https://webdav.smartdrive.web.de and did not have any problems with password encoding. Is this maybe related to https://github.com/nextcloud/server/issues/1731?

[PhilippC]

closing as no response

[antiFetzen]

Please reopen, the issue still exists.

I changed my password it includes umlauts and I couldn't sign in with Keepass2Android.

No Problem with the WebUI, the Clients on Mac, Windows and Android. Sign in to the WebDAV direct by the URL and BasicAuth works find.
I downloaded WebDAV Navigator Lite to try it with a WebDAV client also no problem.

Is there a URI encoding for the password for the request?

@firesoft-de good to know, I have done it this way now. Thanks!

[PhilippC]

can you provide a test account for me?

[antiFetzen]

Here an Account:
https://next.fetzen.rocks

User: philippC
Password: las13iKä9#9w

[PhilippC]

thanks a lot for sharing the credentials. Sorry that I didn't find time to look into this earlier. I just tried to connect (using Cyberduck) but received 405 Method not allowed. How do you test?