I migrated a WebDAV Sync Location from one provider to another.
As I was not sure if this is possible (the server or domain could be part of the encryption or something), I just tested the new location in DEVONthink and could directly see my remote databases.
I then disabled the old location, enabled the new location and tested this with adding a new group in DEVONIthink which then showed up in DTTG without problem!
So far so good.
But …
But after some hours, I tried to use DTTG and got such messages:
Synchronization
https://…/webdav/DT.dtCloud/…/master.plist: forbidden (403)
I then checked DT and saw the same messages in the log:
| 18.07.22, 22:57:48: IP/webdav/DT.dtCloud/inbox/master.plist | forbidden (403) |
|---|---|
| 18.07.22, 22:57:48: IP/webdav/DT.dtCloud/inbox/master.plist | forbidden (403) |
| 18.07.22, 22:58:21: IP/webdav/DT.dtCloud/87c62b1edca53f854feb4b1cb61d392637898af3f213d32644fc55fb3cc7395b/master.plist | forbidden (403) |
| 18.07.22, 22:58:21: IP/webdav/DT.dtCloud/87c62b1edca53f854feb4b1cb61d392637898af3f213d32644fc55fb3cc7395b/master.plist | forbidden (403) |
| 18.07.22, 22:59:40: IP/webdav/DT.dtCloud/f54963f536eaa37d410d20a8f1a3f21e97b32028835ddf7d6330ef478bae6c71/master.plist | forbidden (403) |
| 18.07.22, 22:59:41: IP/webdav/DT.dtCloud/f54963f536eaa37d410d20a8f1a3f21e97b32028835ddf7d6330ef478bae6c71/master.plist | forbidden (403) |
| 18.07.22, 22:59:43: IP/webdav/DT.dtCloud/516147c0dc6347142627f2c366966fc854a29514ed175c67465c9cfe49378edc/master.plist | forbidden (403) |
| 18.07.22, 22:59:43: IP/webdav/DT.dtCloud/516147c0dc6347142627f2c366966fc854a29514ed175c67465c9cfe49378edc/master.plist | forbidden (403) |
I wrote “IP” instead of my IP address above.
Always the same 4 files get logged, each two times in a row.
The sync location has but 5 databases, so one database does NOT show those messages!
The files themself look totally OK to me:
ls */master.plist
-rw-r----- 1 www-data www-data 224 Mar 20 2021 inbox/master.plist
-rw-r----- 1 www-data www-data 224 Mar 20 2021 1ddb5e5df65c2f0c3b49bf3d534a122ed754396682d49bbe7449d9fd67859d56/master.plist
-rw-r----- 1 www-data www-data 224 Mar 27 2021 73161ebfa2ea93a7045848335e75987104884dc4e3c82dd42ba59439339377d8/master.plist
-rw-r----- 1 www-data www-data 224 Jun 29 2021 516147c0dc6347142627f2c366966fc854a29514ed175c67465c9cfe49378edc/master.plist
-rw-r----- 1 www-data www-data 224 Dec 15 2021 87c62b1edca53f854feb4b1cb61d392637898af3f213d32644fc55fb3cc7395b/master.plist
-rw-r----- 1 www-data www-data 224 Jan 24 18:47 f54963f536eaa37d410d20a8f1a3f21e97b32028835ddf7d6330ef478bae6c71/master.plist
EDIT: I think this was caused by some strange error in the Apache configuration where a VirtualHost had not the right certificate … marked as SOLVED