search

buttercup / buttercup-mobile

:iphone: React-Native mobile application for Buttercup
https://buttercup.pw
GNU General Public License v3.0
391 stars 69 forks source link

Cannot add new WebDAV URL to buttercup Android App #353

Closed gschoenberger closed 2 months ago

gschoenberger commented 4 months ago

Hey Buttercup team! Thanks for the great password manager, I am a Buttercup long time user.

Recently adding a new Buttercup WebDAV vault stopped working for me. This is the request on the server side when I try to connect:

91.114.XX.XX XXX.XXX.at - zeus [18/Feb/2024:09:28:54 +0100] "PROPFIND /remote.php/dav/files/zeus/ HTTP/2.0" 207 331 "-" "okhttp/4.9.2" "-" "AT" "TLSv1.3/TLS_AES_256_GCM_SHA384" "63" "0.023"

Return code 207 should be quite OK.

Any hints on how to solve the connection issue? The owncloud instance is served by an Apache2 server behind a NGINX proxy.

If any further details are needed just let me know!

fh-vocalls commented 3 months ago

Hello,

I have got new Android around 8.2.2024 and I still have problem with adding new WebDAV vault (Connection failed - WebDAV connection test failed). On older phone, where vault was added sooner, vault is working properly.

I'm using nextcloud behind nginx proxy (valid tls cert) and on server side I also can see HTTP 207 code, just as @gschoenberger .

It seems it can be same/similar issue as https://github.com/buttercup/buttercup-mobile/issues/352 Desktop app (linux) works without any issue.

If there are other useful information, that would help to figure this out, let me know.

gschoenberger commented 3 months ago

@perry-mitchell Could you give us some hints if we need specific WebDAV settings at NGINX? Currently my work-around is to use Google Drive to sync my Buttercup passwords, but I want definitively go back to WebDAV with owncloud.

Tested on 2 different Android 13 phones (Motorola), WebDAV is not working with the 207 status code on the NGINX side.

THX a lot!

ScribblerCoder commented 3 months ago

same here :/

ModernOctave commented 3 months ago

Hi, even I'm have the same issue...

perry-mitchell commented 3 months ago

This is a known issue and is on our short list to fix. Something has broken on the iOS/Android side, as we haven't made any changes here. I'll try to get to it asap.

Please refrain from me-too posts as it's evident this is now widespread.

Thanks

julianpoemp commented 2 months ago

was fixed in v2.6.2. This issue can be closed.

sousa43 commented 2 months ago

was fixed in v2.6.2. This issue can be closed.

Hi, the problem still exists, even on new equipments on the latest version 2.6.2.

perry-mitchell commented 2 months ago

@sousa43 I can't reproduce this, so I'll close for now. If some manner of reproduction is possible I'll gladly reopen.

sousa43 commented 2 months ago

@perry-mitchell What you need to show to you the problem still exists? Fotos/Videos from every phone i tested? Phones specs? Web dav settings?

I dont want to lose acess to my vault if i change or reset my phone. I know on pc still works but on android not.

perry-mitchell commented 2 months ago

@sousa43 Screenshot of the error, phone specs, and WebDAV settings (if relevant).. obviously without identifying parameters. That'd be a start. Please screenshot your app version too.

If it's evident that it's still this issue, I'll happily reopen.

sousa43 commented 2 months ago

The phone 2 Already has a working vault but if i try adding a new gives the same error of a phone 1. Phone 1 dont have vault.

Webdav Server - Synology NAS with latest version, on a domain with a valid Lets encript certificate.

Phone 2 - Samsung Galaxy Fold 4 Android 14 phone2 1 phone2

Phone1 - Samsung Galaxy M12 Android 13 phone1 phone1 1

I have other phones to test if you need. Already tested with other users and another server but is the same.

julianpoemp commented 2 months ago

@sousa43 perhaps it's a SSL certificate issue. Is the certificate a self-signed certificate? Are you accessing your NAS via a domain or the IP address? Is the certificate still valid?

sousa43 commented 2 months ago

@sousa43 perhaps it's a SSL certificate issue. Is the certificate a self-signed certificate? Are you accessing your NAS via a domain or the IP address? Is the certificate still valid?

Hi @julianpoemp it has a domain with a valid lets encript certificate

perry-mitchell commented 2 months ago

Is it a publicly registered address? If not you probably still need to trust the certificate locally on the device. I'm not super familiar with this process on Android. We added support for self-signed certificates a long time ago and that functionality hasn't been altered, I don't think.

Regardless, this problem isn't related to the original issue I'm afraid. And this is an area that I'm not very familiar with, sorry.