[edit]Whoa, wait a minute. After typing in all of the stuff below in this post, I am wondering if I am confusing a Moon+ WebDAV install/configuration with a KeePass (totally different application!) WebDAV install/configuration. I could very well be. This was done a while back, both applications were configured for WebDAV syncing about the same time. If I have confused Moon+ with KeePass and led you astray, I sincerely apologize. But I don't really remember which app it was.[/edit]
The "Url" and the "Path" work together. The part specified as the "Url" is (functionally) what you see as "[WEBDAV]" down in the "Path" specification.
I do remember that when I set this up in Moon+, that Moon+ initially clobbered my setup. Maybe you are seeing something similar.
On initial set up, I ONLY had a place to specify "Url", "Username" and "Password". There was no place for me to specify "Path". I don't know if this was a display glithc or what, but I remember it clearly.
So I specified the full path to my directory under the "Url" specification. It didn't work (maybe you're stuck at this same place now?) When I went back to this configuration in Moon+ to see if I had made a typo of something, I found that NOW there was a place to specify "Path". And it was populated with the tail end of the specification I had entered into "Url" earlier. BUT, that tail end that Moon+ had automatically used to populate the "Path" setting WAS STILL INCLUDED IN THE "Url" specification. So I manually deleted that tail part from the "Url" specification and left it in the "Path" specification.
The end result of my manual edit left things so the new "Url" specification (my manually edited version) concatenated with the "Path" specification that Moon+ had magically made appear later, equaled the very original full path specification that I had enter into "Url" at the very beginning.
NOW, the syncing worked!
My explanation above was probably very confusing. I'll try to illustrate it below.
What I originally did as my first configuration:
Code:
Url: https://nextcloud.my-domain.my-provider.net/remote.php/dav/files/my-name/Apps/Books
Username: blah,blah,blah
Password: blah,blah,blah
Note that above, Moon+ did not give me any option to enter a "Path". I next tried my sync, and it didn't work. So I went back to Moon+ configuration and this is what I saw:
Code:
Url: https://nextcloud.my-domain.my-provider.net/remote.php/dav/files/my-name/Apps/Books
Username: blah,blah,blah
Password: blah,blah,blah
Path: [WEBDAV]/Apps/Books
Oh look! Moon+ NOW is showing a "Path" entry (that it populated itself). That wasn't there before.
Since the syncing still didn't work, I manually edited the "Url" in the config. So after this edit, things looked like this:
Code:
Url: https://nextcloud.my-domain.my-provider.net/remote.php/dav/files/my-name
Username: blah,blah,blah
Password: blah,blah,blah
Path: [WEBDAV]/Apps/Books
Notice that the "Url" specification is now shorter after I edited it and lopped off the trailing redundant "App/Books" stuff. And the "Path" specification would be the full original "Url" specification if you interpret "[WEBDAV]" to be an ALIAS for the new "Url" entry.
NOW my syncing worked!
I hope this explanation makes sense. After you posted your screenshot of the Moon+ config, that triggered me to remember the issues I had during configuration myself. It was weird. I think Moon+ must have a bug in it's WebDAV configuration that effectively means you have to make a "two pass" configuration attempt. The first pass to enter the actual destination path, and the second pass to manually fix how Moon+ incorrectly interpreted your first pass. Sorry my post here got so long and redundant. I confused myself while typing it, so no telling how badly I confused anybody else trying to read it!
---
Note that above "nextcloud.my-domain.my-provider.net", "my-name", and "Apps/Books" are specific to me and what I did when I set up my NextCloud instance. The "remote.php/dav/file" is specific to NextCloud - that's just what it uses internally when you are accessing it's WebDav built-in server. So your entries for "Url" and "Path" will probably be totally different than mine. But you may have a similar scenario as me where you have a leading and a trailing part of the full access path, and those leading and trailing parts get split in the final "Url" and "Path" components of your specification.