I’m using webDAV to sync between DEVONthink and DEVONthink2Go through a TailScale access. After upgrading from 4.2.1 to 4.2.2, the sync stopped working. WebDAV server responds with HTTP/0.9 instead of HTTP/1. Port setting was ignored — configured 8080, binds to 49248. I Reproduced with: curl -v --http1.1 -X PROPFIND http://100.114.55.128:49248/ -H "Depth: 0"
Are you actually using an unencrypted http:// connection ?
They are using that inside a VPN (Tailscale)
How is that even remotely a DT issue? If your WebDAV server sends the wrong response, that’s the servers problem.
In any case: you’re posting not enough information. Type of WebDAV server, settings in DT/DTTG, all that.
WebDAV sync works just fine with 4.2.2 here with a Synology server, btw.
I was just looking at this and wondered if it could be in play…
I’ll try to dissect the possibilities here. Please take it with a ton of salt, since the OP provided precious little facts.
Tailscale spans a VPN between the machines registered with the same account. So, in the OP’s case, lets assume that they have two machines that get assigned the tailscale IP addresses 100.114.55.128 and 100.114.55.129.
The connections between these machines are completely encrypted and the traffic between them is protectec from prying eyes. Therefore, it’s not strictly necessary to use a https connection to the WebDAV server.
The less secure alternative would be to use a public IP address for the WebDAV serer, possibly through a DynDNS service. Then connect to this IP address from wherever you are. This is less secure since it requires you to pinch a hole in your router, forwarding traffing on the external WebDAV port to the internal one (the two can be identical, you still have to forward the traffic).
Another alternative would be to set up a router-based or WebDAV-server-based VPN. German Fritz! routers provide for WireShark VPNs, Synology offers something similar. Than connect your away machine to the VPN and sync with the local IP of the WebDAV server.
Regardless of the situation: If the WebDAV server replies with a lesser HTTP protocol version than requested, it has a problem. Or the program asking for the HTTP protocol has. I just verified with DT 4.2.2, DTTG 4.0.6 and DTTG 3.latest release. They all have synced just fine in the last several weeks and still do so. No WebDAV issue here.
4 Likes
Apologies for keeping you guys busy, and thank you so much for providing insight into how this all works. The issue was simply that the WebDAV server didn’t start after a reboot. The “Start server on launch” was already set in WebDAVNav Server’s own preferences, but that only starts the server when the app opens — Apparently it doesn’t mean the app itself launches at login. My mistake! I had to add it to the login items. My amateurish look at some output from terminal requests apparently pointed to the port used by Bonjour. And there was a timely coincidence between upgrading to DEVONthink 4.2.2 and rebooting Mac OS, which led me on the wrong path.
1 Like