-
Notifications
You must be signed in to change notification settings - Fork 69
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
New connection to WebDav not working over plain http nor self-signed https (iOS). #324
Comments
Buttercup uses whatever DNS servers are provided by iOS - we don't configure network connections at such a level. Can you resolve your server in safari on the same device? What kind of service do you have that's providing WebDAV, Nginx? Are you sure it's configured properly and you can access it via other apps on other machines in your network? |
Hi, yes I can resolve it just fine in Safari on same device. I can access it via Buttercup for desktop and now I can access it with iOS application but I had to do it via IP address (on desktop I can use domain). Using Nginx with ngx_http_dav_ext_module (to provide PROPFIND method). |
I have the same issue. I do not want to use a public cloud server and therefore use (or try to use) my private nas. |
Hi, |
I have the same issue as well. I am using synology webdav server. If I type a server.localdomain it does not work, if I type the ip it does. I would add that the Buttercup desktop app does not have this issue. |
I've just setup new WebDav server and created a vault there using desktop version of Buttercup - all works perfectly. Buf when I try to add that vault now to iOS app, I'm stuck on the Connection step with testing failing.
I checked both plain http (preferred) and self-signed https and no luck with either of these.
What's strange is that in server's logs (using Nginx in Docker) I don't see any connection attempts whatsoever from the mobile app. I checked accessibility of that url in general by browsing to it in Safari and all works ok. It's like Buttercup isn't even trying to connect, just failing right away.
I then tried with direct IP address and this time it worked. So it makes me think that Buttercup on iOS doesn't use DNS servers that are configured on the connection, but uses some predefined public ones?
The text was updated successfully, but these errors were encountered: