starred/floccus

Fork 0

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

[GH-ISSUE #2011] Linkwarden API route is deprecated, returns 400 error #1343

New issue

Closed

opened 2026-02-25 22:39:44 +03:00 by kerem · 6 comments

kerem commented

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

Owner

Originally created by @emersonveenstra on GitHub (Jul 31, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2011

Which version of floccus are you using?

5.5.6

How many bookmarks do you have, roughly?

360

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

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.

Brave v1.80.125 (Chromium 138.0.7204.184)

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

In github.com/linkwarden/linkwarden@d870ffecd1, Linkwarden deprecated /api/v1/links, and it now returns a 400 error, which breaks syncing.

I created https://github.com/linkwarden/linkwarden/issues/1318 which hopefully will have them revert that change, but wanted to write here as well

Expected Behavior

Syncing works

To Reproduce

Create a linkwarden profile using cloud.linkwarden.app
Attempt to sync bookmarks

Debug log provided

I have provided a debug log file

Originally created by @emersonveenstra on GitHub (Jul 31, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2011 ### Which version of floccus are you using? 5.5.6 ### How many bookmarks do you have, roughly? 360 ### 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. Brave v1.80.125 (Chromium 138.0.7204.184) ### 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 In https://github.com/linkwarden/linkwarden/commit/d870ffecd17125fed051453612acb8d463f75f2d, Linkwarden deprecated `/api/v1/links`, and it now returns a 400 error, which breaks syncing. I created https://github.com/linkwarden/linkwarden/issues/1318 which hopefully will have them revert that change, but wanted to write here as well ### Expected Behavior Syncing works ### To Reproduce 1. Create a linkwarden profile using cloud.linkwarden.app 2. Attempt to sync bookmarks ### Debug log provided - [x] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@emersonveenstra commented on GitHub (Jul 31, 2025):

2025-07-31T13:25:44.120Z Starting sync process for account Toolbar
2025-07-31T13:25:44.122Z Failed to load pending continuation. Continuing with normal sync
2025-07-31T13:25:44.122Z Using "merge default" strategy (no cache available)
2025-07-31T13:25:44.123Z Retrieving local tree
2025-07-31T13:25:44.124Z Overriding title of built-in node 1 Bookmarks => Bookmarks Bar
2025-07-31T13:25:44.124Z Filtering out unaccepted local bookmarks
2025-07-31T13:25:44.124Z Retrieving server tree
2025-07-31T13:25:44.124Z QUEUING GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.124Z FETCHING GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.308Z Receiving response for GET https://cloud.linkwarden.app/api/v1/links?cursor=
2025-07-31T13:25:44.310Z Syncing failed with E019: HTTP status 400. Failed GET request. Check your server configuration and log.

@emersonveenstra commented on GitHub (Jul 31, 2025): ``` 2025-07-31T13:25:44.120Z Starting sync process for account Toolbar 2025-07-31T13:25:44.122Z Failed to load pending continuation. Continuing with normal sync 2025-07-31T13:25:44.122Z Using "merge default" strategy (no cache available) 2025-07-31T13:25:44.123Z Retrieving local tree 2025-07-31T13:25:44.124Z Overriding title of built-in node 1 Bookmarks => Bookmarks Bar 2025-07-31T13:25:44.124Z Filtering out unaccepted local bookmarks 2025-07-31T13:25:44.124Z Retrieving server tree 2025-07-31T13:25:44.124Z QUEUING GET https://cloud.linkwarden.app/api/v1/links?cursor= 2025-07-31T13:25:44.124Z FETCHING GET https://cloud.linkwarden.app/api/v1/links?cursor= 2025-07-31T13:25:44.308Z Receiving response for GET https://cloud.linkwarden.app/api/v1/links?cursor= 2025-07-31T13:25:44.310Z Syncing failed with E019: HTTP status 400. Failed GET request. Check your server configuration and log. ```

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Jul 31, 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 (Jul 31, 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:45 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 31, 2025):

Thank you for investigating I also noticed this recently, but haven't had time to investigate :)

@marcelklehr commented on GitHub (Jul 31, 2025): Thank you for investigating I also noticed this recently, but haven't had time to investigate :)

kerem commented

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

Author

Owner

@daniel31x13 commented on GitHub (Jul 31, 2025):

Hey, I posted a comment over here about what happened, sorry: https://github.com/linkwarden/linkwarden/issues/1318#issuecomment-3140241113

Edit: It's worth mentioning that only the GET method is deprecated, all other routes, sub-routes, and methods are unchanged.

@daniel31x13 commented on GitHub (Jul 31, 2025): Hey, I posted a comment over here about what happened, sorry: https://github.com/linkwarden/linkwarden/issues/1318#issuecomment-3140241113 Edit: It's worth mentioning that only the GET method is deprecated, all other routes, sub-routes, and methods are unchanged.

kerem commented

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

Author

Owner

@daniel31x13 commented on GitHub (Jul 31, 2025):

@marcelklehr I just created a PR which should resolve this issue. Thanks for your work!

@daniel31x13 commented on GitHub (Jul 31, 2025): @marcelklehr I just created a [PR](https://github.com/floccusaddon/floccus/pull/2012) which should resolve this issue. Thanks for your work!

kerem commented

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

Author

Owner

@bellash252 commented on GitHub (Aug 1, 2025):

Nice application Sharp software.

@bellash252 commented on GitHub (Aug 1, 2025): Nice application Sharp software.

kerem referenced this issue

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

[PR #1996] [MERGED] feat(TabGroups): Allow syncing tab groups #1974

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

No description provided.

Rows
Columns