Bookmarks are getting deleted / wrong labeled when using lighttpd and special nextcloud config

[neonblind]

Which version of floccus are you using?

5.8.3

How many bookmarks do you have, roughly?

500

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

No

Sync method

Nextcloud Bookmarks

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

Librewolf 146.0.1-1

Which version of Nextcloud Bookmarks are you using? (if relevant)

v16.0.1

Which version of Nextcloud? (if relevant)

v32.0.3

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

After first sync, creating a new bookmark in Librewolf deletes a random bookmark in Nextcloud Bookmarks but adds the new one with the name from the than deleted.

In the Log attached:
bookmark id 5121;198 is getting 5121;196 with the old name and new url, but 5121;198 was never deleted or moved.

floccus-5.8.3-2026-01-05-redacted.log

Expected Behavior

add new bookmark in the correct folder with the correct label/name, do not delete a random bookmark

To Reproduce

before sync:
folder a - bookmark 1 with name 1 and bookmark 2 with name 2
folder b - bookmark 3 with name 3

adding bookmark 4 with name 4 in folder b

after sync:
folder a - bookmark 1 with name 1
folder b - bookmark 3 with name 3 and bookmark 4 with name 2

bookmark 2 is gone, it's also not in the nextcloud bookmark recycle bin.

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

[marcelklehr]

Hi @neonblind
Thank you for taking the time to give feedback by opening this issue. From a first glance, it seems that there is something going wrong with the specific handling of duplicates in Nextcloud Bookmarks: Nextcloud Bookmarks gives the same ID to multiple bookmarks if they have the same URL. The only way to distinguish them is by the folder they are in. That's why floccus is trying to update the existing bookmark 2 to add it to the new folder b, but somehow folder a got lost in that process it seems. I will look into this.

Many thanks for reducing this to a simple set of instructions to reproduce!

[neonblind]

@marcelklehr
Thank you for looking into it.

Just for clarification. Bookmark 2 and 4 are completely different URLs. There are no duplicates.

[marcelklehr]

Just for clarification. Bookmark 2 and 4 are completely different URLs. There are no duplicates.

Mmh, indeed. That's strange. Floccus asks the server for bookmarks with the URL of bookmark 4 and the server returns bookmark 2 for some reason.

#5121;198[15f67f03246b145d19ab0f58e7c002f72a7cf6ba8563c8de111d2fed915ad1d8](9d6caf944c1c8fb9d7ff7de0dabe266f399545038a5c76e2e6f36e579bf5ca40) parentId: 198
...
2026-01-05T16:58:09.989Z Executing action  { type: 'CREATE',
  payload:   - #undefined[fa3d982889ef8b2e3a35150748b36f2638ed2dff9996bcdd0663964e93335ac5](8e19f08771d947a79d142cc0a4108caa99a3d9aa062d19d1349a44b75afafe7f) parentId: 196,
  index: 2,
  oldItem:   - #0zALWF_mZqUK[fa3d982889ef8b2e3a35150748b36f2638ed2dff9996bcdd0663964e93335ac5](8e19f08771d947a79d142cc0a4108caa99a3d9aa062d19d1349a44b75afafe7f) parentId: wU3P8V_2mvvo }
2026-01-05T16:58:09.990Z (nextcloud-folders)CREATE     - #undefined[fa3d982889ef8b2e3a35150748b36f2638ed2dff9996bcdd0663964e93335ac5](8e19f08771d947a79d142cc0a4108caa99a3d9aa062d19d1349a44b75afafe7f) parentId: 196
2026-01-05T16:58:09.991Z QUEUING GET ###server###nextcloud/index.php/apps/bookmarks/public/rest/v2/bookmark?###url###
2026-01-05T16:58:09.991Z FETCHING GET ###server###nextcloud/index.php/apps/bookmarks/public/rest/v2/bookmark?###url###
2026-01-05T16:58:10.162Z Receiving response for GET ###server###nextcloud/index.php/apps/bookmarks/public/rest/v2/bookmark?###url###
2026-01-05T16:58:10.164Z (nextcloud-folders)UPDATE     - #5121;196[15f67f03246b145d19ab0f58e7c002f72a7cf6ba8563c8de111d2fed915ad1d8](8e19f08771d947a79d142cc0a4108caa99a3d9aa062d19d1349a44b75afafe7f) parentId: 196

[neonblind]

@marcelklehr
Found the issue. Please have a look at this: MichaIng/DietPi#7803

I use lighttpd as webserver.
I wanted to get rid of "index.php" in the url, mainly because of an issue with QOwnNotes nextcloud notes app.

After setting "front_controller_active" => "true" in fastcgi config everything works fine ... well except floccus.

I disabled it now and all the problems with bookmark sync are gone, unfortunately the QOwnNotes issue is back.

When active, what does "front_controller_active" => "true" do with floccus sync to create this mess? :)

[marcelklehr]

Interesting. The search endpoint takes a url GET parameter, perhaps that is overridden by this config at some stage?

[neonblind]

@marcelklehr

attached a log file for the same use case as described above for comparison. maybe you want to look into it.

QOwnNotes now also has an option for opening a note in nextcloud files, which opens the correct note even without "front_controller_active" => "true" in config.

so for now i dont use this option.
maybe lighttpd is not the best choice at all. :)

floccus-5.8.3-2026-01-06-redacted.log

[marcelklehr]

maybe lighttpd is not the best choice at all. :)

Yeah, lighttpd may be doing some funky stuff here. I would recommend nginx