mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #2064] Cannot push new tree, bookmarks are not created #1381
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1381
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @VinterSolen on GitHub (Sep 18, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2064
I have a reverse proxy in front my my stuff.
I have enabled allowing redirect.
No rproxy auth needed (but i wish to have)
I have tried to use the browser credentials to login (for my rproxy i assume?)
Eitherway, it seems its connected, i have the collection "Floccus" on the linkwarden.
When i sync, it finish instantly and nothing created/synced, and no errors
I have also tried to manually trigger uploads
If i set it to Merge, i get the error "E029: Failsafe: The current sync run would delete 100% of your links. Refusing to execute."
If i set it to upload local, nothing happens.
Added redacted logs if it helps floccus-5.7.0-2025-09-17-redacted.log
Originally posted by @VinterSolen in https://github.com/floccusaddon/floccus/discussions/2061
@github-actions[bot] commented on GitHub (Sep 18, 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! 💙
@VinterSolen commented on GitHub (Sep 18, 2025):
I used this userscript to install the linkwarden in my proxmox server https://community-scripts.github.io/ProxmoxVE/scripts?id=linkwarden (shouldn't matter tho?)
After install, i created a user, created an api for floccus to use.
I created the /floccus collection (do upper/lower case matter? im pretty sure i used the same case on floccus as on linkwarden)
@marcelklehr commented on GitHub (Sep 18, 2025):
Hey @VinterSolen
I don't think you did anything wrong, it's most likely a bug in floccus, judging from the logs you posted.
@marcelklehr commented on GitHub (Sep 19, 2025):
Mmh, I cannot reproduce this.
Which browser are you using? Which version of linkwarden?
What do you mean by this? As far as I know you need to create an API key for floccus.
@marcelklehr commented on GitHub (Sep 19, 2025):
Can you try to reset the cache in the settings to trigger a sync from scratch and then try a sync using merge strategy?
@VinterSolen commented on GitHub (Sep 19, 2025):
Brave, with "shields" and uBo disabled for the domain and subdomains i use.
v.2.12.2
I have checked the box yes, doesnt seem to make any difference with if (un)checked
in linkwared i created a
Access Token(api key) to use with floccus, copied and pasted directly from linkwared to floccus.@VinterSolen commented on GitHub (Sep 19, 2025):
Clearing cache doesnt seem to do anything
@marcelklehr commented on GitHub (Sep 21, 2025):
Would you be able to do a bit of debugging? Could you check the network response from Linkwarden?
chrome://extensionsDeveloper modedist/html/background.htmlbutton in floccus' entry next to "Inspect views: "sync nowfor the relevant profile