starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 06:35:59 +03:00

[GH-ISSUE #1935] Sync error due to file size inconsistency #1295

New issue

Closed

opened 2026-02-25 22:39:35 +03:00 by kerem · 9 comments

kerem commented

2026-02-25 22:39:35 +03:00

Owner

Originally created by @injiniero on GitHub (May 2, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1935

Which version of floccus are you using?

5.5.3

How many bookmarks do you have, roughly?

360Kb

Are you using other means to sync bookmarks in parallel to floccus?

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 138.0.1

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

No response

Which version of Nextcloud? (if relevant)

No response

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

cPanel 126.0.16

Describe the Bug

E041: Remote bookmarks file size differs from the content that was actually downloaded from the server. This might be a temporary network issue. If this error persists please contact the server administrator.

Expected Behavior

I expect that the second and next syncs were ok

To Reproduce

I delete the bookmarks xbel file in webdav folder, sync with floccus addon in firefox and the file is uploaded successfully, Trying a second sync causes the above error again.

Debug log provided

I have provided a debug log file

Originally created by @injiniero on GitHub (May 2, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1935 ### Which version of floccus are you using? 5.5.3 ### How many bookmarks do you have, roughly? 360Kb ### Are you using other means to sync bookmarks in parallel to floccus? No ### 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 138.0.1 ### Which version of Nextcloud Bookmarks are you using? (if relevant) _No response_ ### Which version of Nextcloud? (if relevant) _No response_ ### What kind of WebDAV server are you using? (if relevant) cPanel 126.0.16 ### Describe the Bug E041: Remote bookmarks file size differs from the content that was actually downloaded from the server. This might be a temporary network issue. If this error persists please contact the server administrator. ### Expected Behavior I expect that the second and next syncs were ok ### To Reproduce I delete the bookmarks xbel file in webdav folder, sync with floccus addon in firefox and the file is uploaded successfully, Trying a second sync causes the above error again. ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:39:35 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

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

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already.
You can find donation options at https://floccus.org/donate/. Thank you!

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 Nextcloud 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

@github-actions[bot] commented on GitHub (May 2, 2025): 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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings. I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have, as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report and the issue cannot be solved without it, I will have to close the issue after a while. Note also that GitHub in general 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! If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way, I ask that you donate to the project when opening an issue (or at least once your issue is solved), if you're not a donor already. You can find donation options at <https://floccus.org/donate/>. Thank you! 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 Nextcloud 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. Thank you for reading through this primer. I look forward to working with you on this issue! Cheers :blue_heart:

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 2, 2025):

Hello Miguel,
thank you for reporting this! Can you please provide a log file from the floccus settings, so I can see what's going on?

@marcelklehr commented on GitHub (May 2, 2025): Hello Miguel, thank you for reporting this! Can you please provide a log file from the floccus settings, so I can see what's going on?

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@injiniero commented on GitHub (May 2, 2025):

This message repeats several times into the log file:

2025-04-09T15:45:56.478Z Starting sync process for account usuario@xxxxxx.es@webdisk.xxxxx.es
2025-04-09T15:45:56.563Z onSyncStart: begin
2025-04-09T15:45:56.565Z ###server###bookmarks.xbel.lock
2025-04-09T15:45:57.186Z Setting lock: ###server###bookmarks.xbel.lock
2025-04-09T15:45:57.786Z File size mismatch: NaN != 368527
2025-04-09T15:45:57.789Z Syncing failed with E041: Remote bookmarks file size differs from the content that was actually downloaded from the server. This might be a temporary network issue. If this error persists please contact the server administrator.
2025-04-09T15:45:57.797Z onSyncFail
2025-04-09T15:45:57.797Z Freeing lock: ###server###bookmarks.xbel.lock

Seems that the value being compared against the file size gives a NaN

@injiniero commented on GitHub (May 2, 2025): This message repeats several times into the log file: ``` 2025-04-09T15:45:56.478Z Starting sync process for account usuario@xxxxxx.es@webdisk.xxxxx.es 2025-04-09T15:45:56.563Z onSyncStart: begin 2025-04-09T15:45:56.565Z ###server###bookmarks.xbel.lock 2025-04-09T15:45:57.186Z Setting lock: ###server###bookmarks.xbel.lock 2025-04-09T15:45:57.786Z File size mismatch: NaN != 368527 2025-04-09T15:45:57.789Z Syncing failed with E041: Remote bookmarks file size differs from the content that was actually downloaded from the server. This might be a temporary network issue. If this error persists please contact the server administrator. 2025-04-09T15:45:57.797Z onSyncFail 2025-04-09T15:45:57.797Z Freeing lock: ###server###bookmarks.xbel.lock ``` Seems that the value being compared against the file size gives a NaN

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 2, 2025):

Interesting! Could you try doing a HTTP PROPFIND request yourself against the bookmarks.xbel file and post the response here?

@marcelklehr commented on GitHub (May 2, 2025): Interesting! Could you try doing a HTTP PROPFIND request yourself against the bookmarks.xbel file and post the response here?

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@injiniero commented on GitHub (May 3, 2025):

I don't know how to do that request, sorry.

@injiniero commented on GitHub (May 3, 2025): I don't know how to do that request, sorry.

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 3, 2025):

Would you be able to give me an account on your server, perhaps, so I can test myself? You can send me the details via email.

@marcelklehr commented on GitHub (May 3, 2025): Would you be able to give me an account on your server, perhaps, so I can test myself? You can send me the details via email.

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@injiniero commented on GitHub (May 4, 2025):

Thank you, Marcel.
Check your e-mail

The addon was working ok few weeks ago and I changed nothing at server config.

@injiniero commented on GitHub (May 4, 2025): Thank you, Marcel. Check your e-mail The addon was working ok few weeks ago and I changed nothing at server config.

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 4, 2025):

Thank you, Miguel! I was able to identify the problem and will release the fix with the next version of floccus.

@marcelklehr commented on GitHub (May 4, 2025): Thank you, Miguel! I was able to identify the problem and will release the fix with the next version of floccus.

kerem commented

2026-02-25 22:39:36 +03:00

Author

Owner

@injiniero commented on GitHub (May 4, 2025):

Great!
A big Thank you!

@injiniero commented on GitHub (May 4, 2025): Great! A big Thank you!

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#1295

No description provided.

Rows
Columns