Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[iOS] Error with webdav #349

Closed
L42xyz opened this issue Dec 11, 2023 · 6 comments
Closed

[iOS] Error with webdav #349

L42xyz opened this issue Dec 11, 2023 · 6 comments

Comments

@L42xyz
Copy link

L42xyz commented Dec 11, 2023

Hi,

First of all, thanks for this really great app. I have been using Buttercup for years and try to promote it as much as possible!

I recently created a new archive but I can't add the vault on my iPhone. I am using webdav (from Infomaniak) and it works well on my desktop but it does not work on my phone. It refuses to accept the connection. I have tried on multiple iPhones and I can't make it work. I have tried with and without 2FA on webdav and neither of them work.

For information, everything was working before I changed my vault location.

Many thanks in advance

@Yuki21
Copy link

Yuki21 commented Dec 18, 2023

Hi, I can confirm this bug too: I have a self-hosted webdav server, with a valid let's encrypt certificate. It works with my buttercup-desktop application and with the android app, but not with the IOS app.
The app says something like "webdav connection test failed".
Accessing the webdav server from firefox on the same IOS device (using https, as in buttercup) works.

@aa15032261
Copy link

I have the same issue. Existing webdav vaults work but I cant add new ones.

@aa15032261
Copy link

With some digging, it is related to this bug:
perry-mitchell/webdav-client#359

@pilleeins
Copy link

Thanks for the great app. I have the same problem like Yuk21. Please fix. Thank you.

@janborg
Copy link

janborg commented Feb 24, 2024

Same here, not able to add new vaults on new iOS devices!

@Yuki21
Copy link

Yuki21 commented Apr 30, 2024

The bug was fixed by issue #352 , this duplicate issue can therefore be closed now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants