[GH-ISSUE #1595] error: "Syncing failed with The operation was aborted." #1052

Closed
opened 2026-02-25 22:38:51 +03:00 by kerem · 22 comments
Owner

Originally created by @Simplenuity on GitHub (May 8, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1595

Which version of floccus are you using?

5.1.0

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox 113.0.2 (64-bit), Google Chrome 124.0.6367.155 (Official Build) (64-bit), Opera (outdated version) 92.0.4561.43

Which version of Nextcloud Bookmarks are you using? (if relevant)

No response

Which version of Nextcloud? (if relevant)

25.0.8

What kind of WebDAV server are you using? (if relevant)

Nextcloud instance offered by Webo.hosting

Describe the Bug

On all browsers syncing fails with error message
Failed to fetch Last synchronized: 1 week ago

Debug file:

Starting sync process for account
************@nextcloud.webo.host
onSyncStart: begin
Syncing failed with The operation was aborted. 
onSyncFail

Expected Behavior

successful syncing

To Reproduce

trying to sync either via predefined interval or manually invoked

Debug log provided

  • I have provided a debug log file
Originally created by @Simplenuity on GitHub (May 8, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1595 ### Which version of floccus are you using? 5.1.0 ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Firefox 113.0.2 (64-bit), Google Chrome 124.0.6367.155 (Official Build) (64-bit), Opera (outdated version) 92.0.4561.43 ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) 25.0.8 ### What kind of WebDAV server are you using? (if relevant) Nextcloud instance offered by Webo.hosting ### Describe the Bug On all browsers syncing fails with error message `Failed to fetch Last synchronized: 1 week ago` Debug file: ``` Starting sync process for account ************@nextcloud.webo.host onSyncStart: begin Syncing failed with The operation was aborted. onSyncFail ``` ### Expected Behavior successful syncing ### To Reproduce trying to sync either via predefined interval or manually invoked ### Debug log provided - [ ] I have provided a debug log file
kerem 2026-02-25 22:38:51 +03:00
Author
Owner

@github-actions[bot] commented on GitHub (May 8, 2024):

Hello 👋

Thank you for taking the time to open this issue with floccus. I know it's frustrating when software
causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at
and if possible solved.
I'm Marcel and I created floccus and have been maintaining it ever since.
I currently work for Nextcloud which leaves me with less time for side projects like this one
than I used to have.
I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it.
Until then, please be patient.
Note also that GitHub is a place where people meet to make software better together. Nobody here is under any obligation
to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can
collaborate to make this software better. For everyone.
Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge
and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and
try to fix the odd bug yourself. Everyone will be thankful for extra helping hands!
One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum,
to twitter or somewhere else. But this is a technical issue tracker, so please make sure to
focus on the tech and keep your opinions to yourself.

I look forward to working with you on this issue
Cheers 💙

<!-- gh-comment-id:2100126363 --> @github-actions[bot] commented on GitHub (May 8, 2024): Hello :wave: Thank you for taking the time to open this issue with floccus. I know it's frustrating when software causes problems. You have made the right choice to come here and open an issue to make sure your problem gets looked at and if possible solved. I'm Marcel and I created floccus and have been maintaining it ever since. I currently work for Nextcloud which leaves me with less time for side projects like this one than I used to have. I still try to answer all issues and if possible fix all bugs here, but it sometimes takes a while until I get to it. Until then, please be patient. Note also that GitHub is a place where people meet to make software better *together*. Nobody here is under any obligation to help you, solve your problems or deliver on any expectations or demands you may have, but if enough people come together we can collaborate to make this software better. For everyone. Thus, if you can, you could also have a look at other issues to see whether you can help other people with your knowledge and experience. If you have coding experience it would also be awesome if you could step up to dive into the code and try to fix the odd bug yourself. Everyone will be thankful for extra helping hands! One last word: If you feel, at any point, like you need to vent, this is not the place for it; you can go to the forum, to twitter or somewhere else. But this is a technical issue tracker, so please make sure to focus on the tech and keep your opinions to yourself. I look forward to working with you on this issue Cheers :blue_heart:
Author
Owner

@marcelklehr commented on GitHub (May 9, 2024):

You are getting the same error on all Browsers you listed?

<!-- gh-comment-id:2102207184 --> @marcelklehr commented on GitHub (May 9, 2024): You are getting the same error on all Browsers you listed?
Author
Owner

@Simplenuity commented on GitHub (May 9, 2024):

yes, on all of them

<!-- gh-comment-id:2102558853 --> @Simplenuity commented on GitHub (May 9, 2024): yes, on all of them
Author
Owner

@LokChunYu commented on GitHub (May 9, 2024):

chrome,Edge,firefox both the following prompts "This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing."

<!-- gh-comment-id:2102780797 --> @LokChunYu commented on GitHub (May 9, 2024): chrome,Edge,firefox both the following prompts "This profile will be synced soon. We're either waiting for other devices of yours, or other profiles on this device, to finish syncing."
Author
Owner

@marcelklehr commented on GitHub (May 9, 2024):

@LokChunYu This is a different bug, see #1548

<!-- gh-comment-id:2102802684 --> @marcelklehr commented on GitHub (May 9, 2024): @LokChunYu This is a different bug, see #1548
Author
Owner

@marcelklehr commented on GitHub (May 10, 2024):

I'm unable to reproduce this. How many bookmarks do you have? Is there anything special about your setup? Did floccus work before updating to v5.1.0?

<!-- gh-comment-id:2104589836 --> @marcelklehr commented on GitHub (May 10, 2024): I'm unable to reproduce this. How many bookmarks do you have? Is there anything special about your setup? Did floccus work before updating to v5.1.0?
Author
Owner

@LokChunYu commented on GitHub (May 10, 2024):

Worked fine before upgrading v5.1.0, I synced bookmarks via WebDAV URLs with 600+ bookmarks

<!-- gh-comment-id:2104799543 --> @LokChunYu commented on GitHub (May 10, 2024): Worked fine before upgrading v5.1.0, I synced bookmarks via WebDAV URLs with 600+ bookmarks
Author
Owner

@Simplenuity commented on GitHub (May 10, 2024):

I've about 1,500 bookmarks
Setup I'd consider common, nothing special I can think of in regard to Floccus
I sync via WebDAV URL and a XBEL file

I need to roll back to former versions to confirm when the issue started. Will get back to you.

Many thanks for your efforts!

<!-- gh-comment-id:2104875114 --> @Simplenuity commented on GitHub (May 10, 2024): I've about 1,500 bookmarks Setup I'd consider common, nothing special I can think of in regard to Floccus I sync via WebDAV URL and a XBEL file I need to roll back to former versions to confirm when the issue started. Will get back to you. Many thanks for your efforts!
Author
Owner

@Simplenuity commented on GitHub (May 11, 2024):

OK, I did some testing and troubleshooting. Long story short: the XBEL file has been corrupted! It was still readable with an editor but more than half of the content got lost (compared to a backup file).
Maybe of interest: on purpose and after bad experiences (data loss) I only have one browser pushing changes to the file bookmarks.xbel. All other browsers are only allowed to pull the content of bookmarks.xbel while local changes get discarded.

However, it's still not working!

Case 1: bookmarks.xbel file is defined in floccus settings but not created in Nextcloud. Folder path exists.
Result: Syncing runs without obvious error message. Only message is: Last synchronized: 0 seconds ago But bookmarks.xbel is not created.

Case 2: The defined bookmarks.xbel file has been created in Nextcloud (as empty text file)
Result: Syncing fails with error message: E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase?

Log files will be uploaded to your cloud.

<!-- gh-comment-id:2105884923 --> @Simplenuity commented on GitHub (May 11, 2024): OK, I did some testing and troubleshooting. Long story short: the XBEL file has been corrupted! It was still readable with an editor but more than half of the content got lost (compared to a backup file). Maybe of interest: on purpose and after bad experiences (data loss) I only have one browser pushing changes to the file bookmarks.xbel. All other browsers are only allowed to pull the content of bookmarks.xbel while local changes get discarded. However, it's still not working! Case 1: bookmarks.xbel file is defined in floccus settings but not created in Nextcloud. Folder path exists. Result: Syncing runs without obvious error message. Only message is: `Last synchronized: 0 seconds ago` But bookmarks.xbel is not created. Case 2: The defined bookmarks.xbel file has been created in Nextcloud (as empty text file) Result: Syncing fails with error message: `E034: Remote bookmarks file is unreadable. Did you forget to set an encryption passphrase?` Log files will be uploaded to your cloud.
Author
Owner

@marcelklehr commented on GitHub (May 11, 2024):

Thank you for investigating further.

Case 1: The local bookmarks folder seems to be empty, which is why no file is created on the server.

Case 2: The empty file causes the error. The log in this case doesn't help determine what caused the empty file.

<!-- gh-comment-id:2105925924 --> @marcelklehr commented on GitHub (May 11, 2024): Thank you for investigating further. Case 1: The local bookmarks folder seems to be empty, which is why no file is created on the server. Case 2: The empty file causes the error. The log in this case doesn't help determine what caused the empty file.
Author
Owner

@marcelklehr commented on GitHub (May 11, 2024):

on purpose and after bad experiences (data loss)

Nextcloud should be able to keep past versions of the xbel file, which might help. In general, sync is not a backup, of course, so I very much encourage everyone to backup their bookmarks regularly

<!-- gh-comment-id:2105926746 --> @marcelklehr commented on GitHub (May 11, 2024): > on purpose and after bad experiences (data loss) Nextcloud should be able to keep past versions of the xbel file, which might help. In general, sync is not a backup, of course, so I very much encourage everyone to backup their bookmarks regularly
Author
Owner

@marcelklehr commented on GitHub (May 11, 2024):

the XBEL file has been corrupted!

Very strange 🤔

<!-- gh-comment-id:2105927034 --> @marcelklehr commented on GitHub (May 11, 2024): > the XBEL file has been corrupted! Very strange :thinking:
Author
Owner

@Simplenuity commented on GitHub (May 11, 2024):

on purpose and after bad experiences (data loss)

Nextcloud should be able to keep past versions of the xbel file, which might help. In general, sync is not a backup, of course, so I very much encourage everyone to backup their bookmarks regularly

Refreshing to read the clear statement: sync is not a backup

I did and do have backups. So I was able to recover from the data loss :)

<!-- gh-comment-id:2105948656 --> @Simplenuity commented on GitHub (May 11, 2024): > > on purpose and after bad experiences (data loss) > > Nextcloud should be able to keep past versions of the xbel file, which might help. In general, sync is not a backup, of course, so I very much encourage everyone to backup their bookmarks regularly Refreshing to read the clear statement: **sync is not a backup** I did and do have backups. So I was able to recover from the data loss :)
Author
Owner

@Simplenuity commented on GitHub (May 11, 2024):

Thanks for locking into it so quickly!

Case 1: The local bookmarks folder seems to be empty, which is why no file is created on the server.

But it isn't. I can see all the bookmarks as usual via the browser built-in bookmark manager. The local bookmark file of the browser (Opera) is readable and about 1 MB.
I'll do some further testing.

Case 2: The empty file causes the error. The log in this case doesn't help determine what caused the empty file.

Sorry, there might be a misunderstanding. The empty file got created manually to see whether the presence (but without header/syntax) will make a difference when syncing via floccus.

<!-- gh-comment-id:2105953609 --> @Simplenuity commented on GitHub (May 11, 2024): Thanks for locking into it so quickly! > Case 1: The local bookmarks folder seems to be empty, which is why no file is created on the server. But it isn't. I can see all the bookmarks as usual via the browser built-in bookmark manager. The local bookmark file of the browser (Opera) is readable and about 1 MB. I'll do some further testing. > Case 2: The empty file causes the error. The log in this case doesn't help determine what caused the empty file. Sorry, there might be a misunderstanding. The empty file got created manually to see whether the presence (but without header/syntax) will make a difference when syncing via floccus.
Author
Owner

@Simplenuity commented on GitHub (May 11, 2024):

Problem solved!

During my tests I had to restore the folder holding all the bookmarks to be synced and configured under "Folder mapping" in floccus. After the restore I ended up with two folders with the same name. So I deleted the original one which was empty and it got moved to bookmark trash. However, in floccus the path under "Folder mapping" got dynamically adjusted now pointing to the folder in the trash! Setting back the path made floccus pick the correct folder again.

From my end the ticket could be closed.
But

  • @LokChunYu also posted here
  • you still might want to look into some aspects? If you need any testing done, please let me know.

Thank you!

<!-- gh-comment-id:2105960133 --> @Simplenuity commented on GitHub (May 11, 2024): Problem solved! During my tests I had to restore the folder holding all the bookmarks to be synced and configured under "Folder mapping" in floccus. After the restore I ended up with two folders with the same name. So I deleted the original one which was empty and it got moved to bookmark trash. However, in floccus the **path under "Folder mapping" got dynamically adjusted** now pointing to the folder in the trash! Setting back the path made floccus pick the correct folder again. From my end the ticket could be closed. But * @LokChunYu also posted here * you still might want to look into some aspects? If you need any testing done, please let me know. Thank you!
Author
Owner

@Simplenuity commented on GitHub (May 12, 2024):

UPDATE: I need to take back that it can be closed :(

After a few hours of operation incl. one suspend state of machine it's failing again!

  • bookmarks.xbel file is intact (identical with backup)
  • I can see a file bookmarks.xbel.lock with creation date a few hours ago

log file shows:

onSyncStart: begin
https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock
onSyncStart: begin
Syncing failed with Failed to fetch
onSyncFail

after removing the lock file and manually running sync again, it's still failing with this messages in the log file:

onSyncStart: begin
https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock
Setting lock: https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock
Syncing failed with Failed to fetch
onSyncFail
Freeing lock: https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock
<!-- gh-comment-id:2106126204 --> @Simplenuity commented on GitHub (May 12, 2024): UPDATE: I need to take back that it can be closed :( After a few hours of operation incl. one suspend state of machine it's failing again! * bookmarks.xbel file is intact (identical with backup) * I can see a file bookmarks.xbel.lock with creation date a few hours ago log file shows: ``` onSyncStart: begin https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock onSyncStart: begin Syncing failed with Failed to fetch onSyncFail ``` after removing the lock file and manually running sync again, it's still failing with this messages in the log file: ``` onSyncStart: begin https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock Setting lock: https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock Syncing failed with Failed to fetch onSyncFail Freeing lock: https://nextcloud.webo.hosting/remote.php/webdav/bookmarks/bookmarks.xbel.lock ```
Author
Owner

@marcelklehr commented on GitHub (May 12, 2024):

Huh, could you open the debugger in your browser to check what happens to the network request here?

The following are the steps to do that:

Firefox

  • Go to about:debugging
  • go to "This firefox"
  • click on Inspect button next to floccus entry
  • go to the network tab in the inspector
  • trigger a sync by clicking the sync now button for the account of your choice.
  • check the failing network requests

Chrome

  • Go to chrome://extensions
  • enable Developer mode
  • click on Service worker link in floccus' entry next to "Inspect views: "
  • go to the network tab in the inspector window
  • trigger a sync by clicking the sync now button for the account of your choice
  • check the failing network requests
<!-- gh-comment-id:2106157035 --> @marcelklehr commented on GitHub (May 12, 2024): Huh, could you open the debugger in your browser to check what happens to the network request here? The following are the steps to do that: #### Firefox * Go to `about:debugging` * go to "This firefox" * click on `Inspect` button next to floccus entry * go to the network tab in the inspector * trigger a sync by clicking the `sync now` button for the account of your choice. * check the failing network requests #### Chrome * Go to `chrome://extensions` * enable `Developer mode` * click on `Service worker` link in floccus' entry next to "Inspect views: " * go to the network tab in the inspector window * trigger a sync by clicking the `sync now` button for the account of your choice * check the failing network requests
Author
Owner

@Simplenuity commented on GitHub (May 12, 2024):

Hi @marcelklehr, I've uploaded screenshots to your cloud.
In case it's relevant:
Opera: configured as push only
Firefox: configured as pull only

<!-- gh-comment-id:2106205534 --> @Simplenuity commented on GitHub (May 12, 2024): Hi @marcelklehr, I've uploaded screenshots to your cloud. In case it's relevant: Opera: configured as push only Firefox: configured as pull only
Author
Owner

@marcelklehr commented on GitHub (May 12, 2024):

It seems that the issue is a NS_ERROR_NET_PARTIAL_TRANSFER, so I'm guessing something is wrong with the network between floccus and your nextcloud that causes a mere partial transfer of the file. Since floccus is on the receiving end, there's not much I can do here. I recommend contacting your hoster.

<!-- gh-comment-id:2106210513 --> @marcelklehr commented on GitHub (May 12, 2024): It seems that the issue is a NS_ERROR_NET_PARTIAL_TRANSFER, so I'm guessing something is wrong with the network between floccus and your nextcloud that causes a mere partial transfer of the file. Since floccus is on the receiving end, there's not much I can do here. I recommend contacting your hoster.
Author
Owner

@Simplenuity commented on GitHub (May 12, 2024):

Thanks @marcelklehr for taking the time.
I'll test some network related settings and report back if I can find anything relevant.

<!-- gh-comment-id:2106212336 --> @Simplenuity commented on GitHub (May 12, 2024): Thanks @marcelklehr for taking the time. I'll test some network related settings and report back if I can find anything relevant.
Author
Owner

@Simplenuity commented on GitHub (May 12, 2024):

@marcelklehr, positive news:

  • TL;DR:
    it's working again!

  • long version:
    While testing some network settings I noticed a change in error messages - and that my file manager's webdav connection to the server went down. Checking the login page it turned out that the server had been taken into maintenance mode! Meanwhile it's back up - and floccus sync is working as expected. I assume(!) the server had been in a degraded state quite some time before the service completely shut down.

I'll monitor the situation closely for some time.

<!-- gh-comment-id:2106253052 --> @Simplenuity commented on GitHub (May 12, 2024): @marcelklehr, positive news: * TL;DR: **it's working again**! * long version: While testing some network settings I noticed a change in error messages - and that my file manager's webdav connection to the server went down. Checking the login page it turned out that the server had been taken into maintenance mode! Meanwhile it's back up - and floccus sync is working as expected. I assume(!) the server had been in a degraded state quite some time before the service completely shut down. I'll monitor the situation closely for some time.
Author
Owner

@github-actions[bot] commented on GitHub (May 14, 2025):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

<!-- gh-comment-id:2878265290 --> @github-actions[bot] commented on GitHub (May 14, 2025): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/floccus#1052
No description provided.