starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-25 14:16:12 +03:00

[GH-ISSUE #2146] Sync not working due to Failsafe? The current sync run would delete X% of your local links in this profile #1442

New issue

Closed

opened 2026-02-25 22:40:01 +03:00 by kerem · 5 comments

kerem commented

2026-02-25 22:40:01 +03:00

Owner

Originally created by @jero1110 on GitHub (Jan 4, 2026).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2146

Which version of floccus are you using?

5.8.3

How many bookmarks do you have, roughly?

250

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

On Android smartphone

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.

Brave

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)

webdav to pcloud.com

Describe the Bug

Sync on Linux Desktop not working. Sometims it is working when shutting down VPN.

Expected Behavior

Sync while VPN is working

To Reproduce

Debug log provided

I have provided a debug log file

Originally created by @jero1110 on GitHub (Jan 4, 2026). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2146 # ### Which version of floccus are you using? 5.8.3 ### How many bookmarks do you have, roughly? 250 ### Are you using other means to sync bookmarks in parallel to floccus? On Android smartphone ### 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. Brave ### 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) webdav to pcloud.com ### Describe the Bug Sync on Linux Desktop not working. Sometims it is working when shutting down VPN. ### Expected Behavior Sync while VPN is working ### To Reproduce <img width="1290" height="852" alt="Image" src="https://github.com/user-attachments/assets/91832723-32c6-4a9b-9a55-a12d6aae828b" /> ### Debug log provided - [x] I have provided a debug log file

kerem

2026-02-25 22:40:01 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:40:02 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 4, 2026):

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 (Jan 4, 2026): 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:40:02 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jan 4, 2026):

Hi @jero1110
Thank you for taking the time to give feedback by opening this issue. It seems that for you the failsafe is kicking in, which prevents floccus from unintended deletion of too much data. This may happen because somehow the file on your server got emptied. For now, I don't think this is related to VPN.

If the local bookmarks in the browser that you made the screenshot in are correct, You can

Go to the floccus profile settings
Disable the failsafe
Set the sync strategy to "Upload local changes and revert changes from other browsers".
Click "Save"
Then click sync in the floccus overview panel. This will push the state of your bookmarks on that browser to pcloud, after that normal sync should succeed again without the failsafe kicking in.
That means you can Enable the failsafe again now and set sync strategy back to merge.

If, on the other hand, the state on pcloud is the correct version of your set of bookmarks (you can check this by opening the file that is stored on pcloud in a text editor, as long as you don't sync with end-to-end encryption), you can

Go to the floccus profile settings
Disable the failsafe
Set the sync strategy to "Revert local changes and download changes from other browsers".
Click "Save"
Then click sync in the floccus overview panel. This will force the current state of the server onto your browser, after that normal sync should succeed again without the failsafe kicking in.
That means you can Enable the failsafe again now and set sync strategy back to merge.

PS: I sadly cannot download the log file you uploaded. Could you try that again? There's also a redacted log option, which doesn't give away all your full URL in clear text. (This is a public site.)

@marcelklehr commented on GitHub (Jan 4, 2026): Hi @jero1110 Thank you for taking the time to give feedback by opening this issue. It seems that for you the failsafe is kicking in, which prevents floccus from unintended deletion of too much data. This may happen because somehow the file on your server got emptied. For now, I don't think this is related to VPN. If the local bookmarks in the browser that you made the screenshot in are correct, You can 1. Go to the floccus profile settings 2. Disable the failsafe 3. Set the sync strategy to "Upload local changes and revert changes from other browsers". 4. Click "Save" 5. Then click sync in the floccus overview panel. This will push the state of your bookmarks on that browser to pcloud, after that normal sync should succeed again without the failsafe kicking in. 6. That means you can Enable the failsafe again now and set sync strategy back to merge. If, on the other hand, the state on pcloud is the correct version of your set of bookmarks (you can check this by opening the file that is stored on pcloud in a text editor, as long as you don't sync with end-to-end encryption), you can 1. Go to the floccus profile settings 2. Disable the failsafe 3. Set the sync strategy to "Revert local changes and download changes from other browsers". 4. Click "Save" 5. Then click sync in the floccus overview panel. This will force the current state of the server onto your browser, after that normal sync should succeed again without the failsafe kicking in. 6. That means you can Enable the failsafe again now and set sync strategy back to merge. PS: I sadly cannot download the log file you uploaded. Could you try that again? There's also a redacted log option, which doesn't give away all your full URL in clear text. (This is a public site.)

kerem commented

2026-02-25 22:40:02 +03:00

Author

Owner

@jero1110 commented on GitHub (Jan 4, 2026):

Danke!! Hat funktioniert!
Beste Grüße
Jens Rose

Am 4. Januar 2026 12:18:03 MEZ schrieb Marcel Klehr @.***>:

marcelklehr left a comment (floccusaddon/floccus#2146)

Hi @jero1110
Thank you for taking the time to give feedback by opening this issue. It seems that for you the failsafe is kicking in, which prevents floccus from unintended deletion of too much data. This may happen because somehow the file on your server got emptied.

If the local bookmarks in the browser that you made the screenshot in are correct, You can

Go to the floccus profile settings

Disable the failsafe

Set the sync strategy to "Upload local changes and revert changes from other browsers".

Click "Save"

Then click sync in the floccus overview panel. This will push the state of your bookmarks on that browser to pcloud, after that normal sync should succeed again without the failsafe kicking in.

That means you can Enable the failsafe again now and set sync strategy back to merge.

If, on the other hand, the state on pcloud is the correct version of your set of bookmarks (you can check this by opening the file that is stored on pcloud in a text editor, as long as you don't sync with end-to-end encryption), you can

Go to the floccus profile settings

Disable the failsafe

Set the sync strategy to "Revert local changes and download changes from other browsers".

Click "Save"

Then click sync in the floccus overview panel. This will force the current state of the server onto your browser, after that normal sync should succeed again without the failsafe kicking in.

That means you can Enable the failsafe again now and set sync strategy back to merge.

PS: I sadly cannot download the log file you uploaded. Could you try that again? There's also a redacted log option, which doesn't give away all your full URL in clear text. (This is a public site.)

--
Reply to this email directly or view it on GitHub:
https://github.com/floccusaddon/floccus/issues/2146#issuecomment-3707992478
You are receiving this because you were mentioned.

Message ID: @.***>

@jero1110 commented on GitHub (Jan 4, 2026): Danke!! Hat funktioniert! Beste Grüße Jens Rose Am 4. Januar 2026 12:18:03 MEZ schrieb Marcel Klehr ***@***.***>: >marcelklehr left a comment (floccusaddon/floccus#2146) > >Hi @jero1110 >Thank you for taking the time to give feedback by opening this issue. It seems that for you the failsafe is kicking in, which prevents floccus from unintended deletion of too much data. This may happen because somehow the file on your server got emptied. > >If the local bookmarks in the browser that you made the screenshot in are correct, You can > >1. Go to the floccus profile settings >2. Disable the failsafe >3. Set the sync strategy to "Upload local changes and revert changes from other browsers". >4. Click "Save" >5. Then click sync in the floccus overview panel. This will push the state of your bookmarks on that browser to pcloud, after that normal sync should succeed again without the failsafe kicking in. >6. That means you can Enable the failsafe again now and set sync strategy back to merge. > >If, on the other hand, the state on pcloud is the correct version of your set of bookmarks (you can check this by opening the file that is stored on pcloud in a text editor, as long as you don't sync with end-to-end encryption), you can > >1. Go to the floccus profile settings >2. Disable the failsafe >3. Set the sync strategy to "Revert local changes and download changes from other browsers". >4. Click "Save" >5. Then click sync in the floccus overview panel. This will force the current state of the server onto your browser, after that normal sync should succeed again without the failsafe kicking in. >6. That means you can Enable the failsafe again now and set sync strategy back to merge. > >PS: I sadly cannot download the log file you uploaded. Could you try that again? There's also a redacted log option, which doesn't give away all your full URL in clear text. (This is a public site.) > >-- >Reply to this email directly or view it on GitHub: >https://github.com/floccusaddon/floccus/issues/2146#issuecomment-3707992478 >You are receiving this because you were mentioned. > >Message ID: ***@***.***>

kerem commented

2026-02-25 22:40:02 +03:00

Author

Owner

@jero1110 commented on GitHub (Jan 4, 2026):

The log file...

Am 04.01.2026 12:18 schrieb Marcel Klehr:

MARCELKLEHR left a comment (floccusaddon/floccus#2146) [1]

Hi @jero1110 [2]
Thank you for taking the time to give feedback by opening this issue.
It seems that for you the failsafe is kicking in, which prevents
floccus from unintended deletion of too much data. This may happen
because somehow the file on your server got emptied.

If the local bookmarks in the browser that you made the screenshot in
are correct, You can

* Go to the floccus profile settings
* Disable the failsafe
* Set the sync strategy to "Upload local changes and revert changes
from other browsers".
* Click "Save"
* Then click sync in the floccus overview panel. This will push the
state of your bookmarks on that browser to pcloud, after that normal
sync should succeed again without the failsafe kicking in.
* That means you can Enable the failsafe again now and set sync
strategy back to merge.

If, on the other hand, the state on pcloud is the correct version of
your set of bookmarks (you can check this by opening the file that is
stored on pcloud in a text editor, as long as you don't sync with
end-to-end encryption), you can

* Go to the floccus profile settings
* Disable the failsafe
* Set the sync strategy to "Revert local changes and download
changes from other browsers".
* Click "Save"
* Then click sync in the floccus overview panel. This will force the
current state of the server onto your browser, after that normal sync
should succeed again without the failsafe kicking in.
* That means you can Enable the failsafe again now and set sync
strategy back to merge.

PS: I sadly cannot download the log file you uploaded. Could you try
that again? There's also a redacted log option, which doesn't give
away all your full URL in clear text. (This is a public site.)

--
Reply to this email directly, view it on GitHub [1], or unsubscribe
[3].
You are receiving this because you were mentioned.Message ID:
@.***>

Links:

[1]
https://github.com/floccusaddon/floccus/issues/2146#issuecomment-3707992478
[2] https://github.com/jero1110
[3]
https://github.com/notifications/unsubscribe-auth/B4JHNQH6LNHREPZDVTILWPL4FDZGXAVCNFSM6AAAAACQUOVUNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBXHE4TENBXHA

@jero1110 commented on GitHub (Jan 4, 2026): The log file... Am 04.01.2026 12:18 schrieb Marcel Klehr: > MARCELKLEHR left a comment (floccusaddon/floccus#2146) [1] > > Hi @jero1110 [2] > Thank you for taking the time to give feedback by opening this issue. > It seems that for you the failsafe is kicking in, which prevents > floccus from unintended deletion of too much data. This may happen > because somehow the file on your server got emptied. > > If the local bookmarks in the browser that you made the screenshot in > are correct, You can > > * Go to the floccus profile settings > * Disable the failsafe > * Set the sync strategy to "Upload local changes and revert changes > from other browsers". > * Click "Save" > * Then click sync in the floccus overview panel. This will push the > state of your bookmarks on that browser to pcloud, after that normal > sync should succeed again without the failsafe kicking in. > * That means you can Enable the failsafe again now and set sync > strategy back to merge. > > If, on the other hand, the state on pcloud is the correct version of > your set of bookmarks (you can check this by opening the file that is > stored on pcloud in a text editor, as long as you don't sync with > end-to-end encryption), you can > > * Go to the floccus profile settings > * Disable the failsafe > * Set the sync strategy to "Revert local changes and download > changes from other browsers". > * Click "Save" > * Then click sync in the floccus overview panel. This will force the > current state of the server onto your browser, after that normal sync > should succeed again without the failsafe kicking in. > * That means you can Enable the failsafe again now and set sync > strategy back to merge. > > PS: I sadly cannot download the log file you uploaded. Could you try > that again? There's also a redacted log option, which doesn't give > away all your full URL in clear text. (This is a public site.) > > -- > Reply to this email directly, view it on GitHub [1], or unsubscribe > [3]. > You are receiving this because you were mentioned.Message ID: > ***@***.***> > > Links: > ------ > [1] > https://github.com/floccusaddon/floccus/issues/2146#issuecomment-3707992478 > [2] https://github.com/jero1110 > [3] > https://github.com/notifications/unsubscribe-auth/B4JHNQH6LNHREPZDVTILWPL4FDZGXAVCNFSM6AAAAACQUOVUNWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMBXHE4TENBXHA

kerem commented

2026-02-25 22:40:02 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jan 4, 2026):

Danke!! Hat funktioniert!

Yay, then the log file is not necessary anymore :) Happy syncing!

@marcelklehr commented on GitHub (Jan 4, 2026): > Danke!! Hat funktioniert! Yay, then the log file is not necessary anymore :) Happy syncing!

kerem referenced this issue

2026-02-25 23:31:08 +03:00

[PR #1442] [CLOSED] build(deps): bump postcss and vue-loader #1887

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

No description provided.

Rows
Columns