starred/floccus

Fork 0

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

[GH-ISSUE #1874] Sync does not resume when server was temporarily unreachable #1256

New issue

Closed

opened 2026-02-25 22:39:28 +03:00 by kerem · 2 comments

kerem commented

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

Owner

Originally created by @tom709 on GitHub (Mar 5, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1874

Which version of floccus are you using?

5.4.4

How many bookmarks do you have, roughly?

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/Linux

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)

nginx

Describe the Bug

When I roam into a network where my webdav server is not reachable and then return to the network where it is, Floccus does not seem to attempt to sync, even when I restart Firefox. It says "not synced for x days" and only syncs once I press the sync button (I did wait several hours; my sync interval is 15min).

This is a new problem; I did not see it with Floccus 4.x.

Expected Behavior

It can be argued whether Floccus should retry periodically when the server does not respond, but at least when I restart Firefox I would expect it to retry, which does not seem to happen, at least not always.

To Reproduce

see above

floccus-5.4.4-2025-03-05-redacted.log

Debug log provided

I have provided a debug log file

Originally created by @tom709 on GitHub (Mar 5, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1874 ### Which version of floccus are you using? 5.4.4 ### How many bookmarks do you have, roughly? 5k ### 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/Linux ### 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) nginx ### Describe the Bug When I roam into a network where my webdav server is not reachable and then return to the network where it is, Floccus does not seem to attempt to sync, even when I restart Firefox. It says "not synced for x days" and only syncs once I press the sync button (I did wait several hours; my sync interval is 15min). This is a new problem; I did not see it with Floccus 4.x. ### Expected Behavior It can be argued whether Floccus should retry periodically when the server does not respond, but at least when I restart Firefox I would expect it to retry, which does not seem to happen, at least not always. ### To Reproduce see above [floccus-5.4.4-2025-03-05-redacted.log](https://github.com/user-attachments/files/19089385/floccus-5.4.4-2025-03-05-redacted.log) ### Debug log provided - [x] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Mar 5, 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.
I'm Marcel and I created floccus a few years ago, 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!
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.

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

@github-actions[bot] commented on GitHub (Mar 5, 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. I'm Marcel and I created floccus a few years ago, 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! 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. I look forward to working with you on this issue Cheers :blue_heart:

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Mar 5, 2025):

Thanks for the feedback! It depends a bit on how long the server was unreachable. Floccus employs an exponential backoff strategy, that will wait in increasingly longer intervals as the server downtime gets longer. Currently this backoff is unbounded, but it would make sense to cap it at something like a few hours.

@marcelklehr commented on GitHub (Mar 5, 2025): Thanks for the feedback! It depends a bit on how long the server was unreachable. Floccus employs an exponential backoff strategy, that will wait in increasingly longer intervals as the server downtime gets longer. Currently this backoff is unbounded, but it would make sense to cap it at something like a few hours.

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

No description provided.

Rows
Columns