Rclone bisync works on in-progress fork? #2706
Replies: 1 comment
|
With the latest commits in https://github.com/opencloud-eu/rclone/tree/add-vendor-opencloud and the latest opencloud release (7.2.0) rclone bisync should work. Obviously the same disclaimers that are mentioned on the upstream rclone docs (https://rclone.org/commands/rclone_bisync/) do apply |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I've noticed efforts to add OpenCloud as a rclone vendor, and out of curiosity I cloned the
add-vendor-opencloudbranch from the rclone fork available at https://github.com/opencloud-eu/rclone to see if an issue I have when runningrclone bisyncstill occurs. And it seems it does. Though I don't know if it's a OpenCloud issue or rclone issue.The OpenCloud server is returning 401 unauthorized errors sometimes, and
rclone bisyncdoesn't tolerate these errors. Is there someone that experienced this before? Are there any settings or command options I could use as a workaround?Thanks!
All reactions