owncloud “connection closed operation canceled” tip

I’ve been having problems with owncloud syncing properly. I keep getting “connection closed,” “operation canceled” errors. I finally figured out something that works for me: I go into the client and change the download bandwidth from “No limit” to 99999 KBytes/s. Apparently, there’s some niggling bug that this works around. The limit can be set as high as you want and it still works.

[EDIT] This doesn’t appear to be working the way I thought it would. I am still hoping that this will be taken care of in the next release.

4 Comments

  1. parcher author

    April 23, 2015

    FYI, I thought this would take care of the problem, but it’s been sporadic at best. Sometimes it helps, sometimes it doesn’t.
    It does seem that once the initial sync is done (8GB or so), then I don’t have any more problems.

    • parcher author

      March 16, 2016

      Two things:
      1) It seems that the problem has been resolved in the latest versions of the client. I haven’t had any issues, anyway.
      2) I found that if you are populating a new client with an existing repository, doing an rsync from another client or even from the source machine is faster than the initial owncloud sync. Once the rsync is done, then owncloud recognizes the files as being up to date.

  2. Dan Sawyer

    January 25, 2016

    This worked for me. Thank you. Dan

  3. Sam

    March 12, 2016

    Sometimes pausing and unpausing the sync is enough, I’ve found.

Share Your Thoughts