Hi,
I try to link via WebDav my Synology NAS.
Access via Webdav/https on port 5006 is working (from the internet) via “Total Commander” => so the NAS (+ Router) are setup correctly. I did not have to use a certificate for this.
When I try to link storage via WebDAV in oDrive (using exactly the same address:port, usernam and password that work in Total commander), I get either an error “Cannot connect to WebDAV server. Check your internet connection and try again.” (with option “require valis ssl certificate” disabled) or I get an error “Invalid SSL certificate. Name Mismatch.” (with option “require valid ssl certificate” enabled).
I checked the certificate on the synology NAS: name seems correct (i.e. that name I use for the connection), that cert is configured to be used for WebDAV and the certificate is (still) valid…
Anyone any idea? I prefer to have oDrive instead of the “heavy” Synology Drive client to be able to share my documents between my wife’s and mine laptop…
Hi @hofmannj,
I don’t have a Synology NAS to test with, but if you can provide a test account on your internet-accessible NAS, I can try to see what the issue is with linking.
Hi Tony - thanks - will do this in the evening/after work (now 8:00 in Germany)… hope you can find it.
Probably I need 1h+ to figure out how to setup another user on the NAS and bind it to a certain folder/over Webdav (and of course trying first that with a webDAv client this new account works . I’ll post you…
J.
Hi Tony, the NAS is prepared - if you send me an email (hofmannj@outlook.de) I’ll send you the path, the user and the password…
As you can see in the attachments (last picture in next post as I’m not allowed to post more than 2 media ), access over WebDAV (via mobile) using Total commander “works like a charm” - just the path, user & password… I hope you can find it why odrive doesn’t want to link…
Hey @hofmannj,
I took a look at this. What is strange is that it works fine when debugging locally on my system, but not once it gets pushed to our backend.
It looks like it has something to do with the name resolution. It is taking a long time (~30 seconds). It is not clear why, at this point.
Immediate workaround:
You can use the IP address of your NAS instead of the hostname. You will need to disable certificate validation since the names will not match.
Future:
I have added a few fixes for the next release. These will address the previous certificate validation error you were seeing and will also allow you to continue connecting even if our backend has an issue. The latter fix will allow you to use the desktop client, which does not exhibit the same timeout issue I am seeing on the backend.
I’ll keep poking around, but this is a tricky one. I am only seeing this behavior for your particular host… it is really odd.
Hi Tony,
thanks - I already started doubting that I screwed up something (I tried this now several times for months).
Using the IP address is not really a help (DT retail subscribers like me get a new IP on each new DSL connection)… but I can wait for the fix you mentioned. Any idea about “when” this may be available (your’re doing Scrum/agile? 2-4 weeks?).
Regarding “behavior for your particular host”: that is a pretty normal (standard) Synology NAS 418 (there are >> 10k of then all over the world I’m pretty sure) with the latest Synology OS (DSM 7 - I had the same behaviour with DSM 6)… so the the fix would probably help a lot more peaople…
THANKS
J.
The web access is very slow, but you should be able to link (while verifying the SSL cert) by selecting “Continue Anyway”. Browsing via the web is possible but slow. Desktop client access should be just fine, though.
Works now! Great!
(I’m so stupid - I just didn’t recognize before the “link anyway”.)
And the speed in the windows client is really nice/more than sufficient - thanks.
Can be marked as “solved” imho.
. I’ll post you…
), access over WebDAV (via mobile) using Total commander “works like a charm” - just the path, user & password… I hope you can find it why odrive doesn’t want to link…
