Floccus addon with Linkwarden is not working on Chrome 142.0.7444.60 (macos)

[SuberSeb]

Which version of floccus are you using?

5.6.0

How many bookmarks do you have, roughly?

100

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

No

Sync method

Linkwarden

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

Chrome 142.0.7444.60

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)

No response

Describe the Bug

After Chrome update to 142.0.7444.60 sync is not working anymore. I use Floccus with Linkwarden. No any configuration was changed recently. Also tried to recreate the profile.

Logs:
2025-11-05T04:42:21.114Z Starting sync process for account Linkwarden
2025-11-05T04:42:21.118Z Using "merge default" strategy (no cache available)
2025-11-05T04:42:21.118Z Retrieving local tree
2025-11-05T04:42:21.130Z Overriding title of built-in node 1 Панель закладок => Bookmarks Bar
2025-11-05T04:42:21.135Z Filtering out unaccepted local bookmarks
2025-11-05T04:42:21.135Z Retrieving server tree
2025-11-05T04:42:21.135Z QUEUING GET http://192.168.1.45:23700/api/v1/search?searchQueryString=&cursor=
2025-11-05T04:42:21.135Z FETCHING GET http://192.168.1.45:23700/api/v1/search?searchQueryString=&cursor=
2025-11-05T04:42:21.143Z Syncing failed with E017: Network error: Check your network connection and your account details

For some reason syncing is failed. But if I open the link http://192.168.1.45:23700/api/v1/search?searchQueryString=&cursor= manually with the same browser it's working and I see the API response. So doesn't seems to be a real network issue.

Linkwarden v2.13.1.

Expected Behavior

Sync is working ok.

To Reproduce

Just try to sync with Linkwarden.

Debug log provided

• I have provided a debug log file

[github-actions]

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! 💙

[michilyy]

I also experience the same bug.
I am using Floccus Android 5.7.0 with linkwarden v2.13.1.
Strangely enough Firefox 144.0.2 (64-Bit) still works.

Update: I added a new bookmark with Firefox and then tried syncing again on Android.
It synced correctly so I am not sure what exactly causes this bug.

[mayziran]

This is still the case on windows. I found that when my chrome was updated to version 142, synchronization failed.

[marcelklehr]

Hi everyone!
Thank you for taking the time to give feedback by opening this issue! I'll try to help get to the bottom of this.
Are you all using bare HTTP (ie. no HTTPS)?

[mayziran]

Hi everyone! Thank you for taking the time to give feedback by opening this issue! I'll try to help get to the bottom of this. Are you all using bare HTTP (ie. no HTTPS)?

It seems to be entirely a chrome version issue, I updated chrome again today and all issues have been fixed!

[marcelklehr]

Oh, wow.