Devonthink Sync 403 forbidden

DEVONthink
21

Ok thanks for that tip. I believe the corresponding log message is "8 Failed Downloads, 0 Invalid Checksums)

Hard to tell sometimes what error log corresponds to what :sweat:

image
image1223Ɨ482 205 KB

22

No problem.
Did you do the thorough verification?

  • Do you happen to be running a VPN?
    • If so, which one?
23

Yes thorough verification (saw it when it was halfway done but didnā€™t stick around to watch it complete)
No VPN

24

And what was finally reported in the Log window?

25

I was assuming the ā€œ8 failed downloadsā€¦ā€ mentioned above was the outcome

26

Thanks. It wasnā€™t clear if this was the tail end of the log.

If you know what database isnā€™t syncing, select the sync location, then Control-click the database in the Databases list on the right, and choose Clean Database.
After the clean has been successfully reported in the Log window, enable syncing the database again.

27

Cleaning seems to have solved the problem thanks

28

Youā€™re welcome.

29

This has continued recurring every couple months, the master.plist file not syncing due to forbidden 403.

The database is 3GB. It takes all day to Clean Database due to slow connection. Is there something else I can do, or a way to prevent this?

Iā€™m warned when I click ā€œclean databaseā€ that some items arenā€™t downloaded. Does that mean cleaning will erase them? How can I track down what items those are?

Sync was finally working in the background after I gave up bonjour. I just need one of them to work consistently. Iā€™m almost a year into using DT and still spending about an hour every week fixing sync problems. Is there a most reliable sync setup?

30

Sure, Bonjour.

31

Thatā€™s what I assumed. I was willing to give up remote sync, and had for months. But bonjour would never do background syncing. If I wanted it to sync, I had to click the little cloud on mobile devices and stand there and watch it work. The remote sync stores have been much better at syncing automatically.

32

From my experience and our tickets, this isnā€™t a sync issue. Itā€™s a WebDAV issue and one that sporadically occurs and goes away. Iā€™ve even seen it when I ran internal WebDAV via OS X Server.

33

It would be nice to have a notice in the manual, or a warning when the option is selected, when there are known issues like this.

34

It is not a consistent or controllable event. Documenting it in the manual would make it appear to be an expected or inherent issue, which isnā€™t the case. Also, weā€™d have to document such potentials for any sync method. Seeing as itā€™s not something that happens to all people often, we have chosen to address it one-on-one as needed.

1 Like