starred/floccus

Fork 0

mirror of https://github.com/floccusaddon/floccus.git synced 2026-04-26 14:45:59 +03:00

[GH-ISSUE #2117] Nextcloud E020: Could not parse server response #1421

New issue

Closed

opened 2026-02-25 22:39:58 +03:00 by kerem · 4 comments

kerem commented

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

Owner

Originally created by @exu-g on GitHub (Dec 10, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2117

Which version of floccus are you using?

5.8.2

How many bookmarks do you have, roughly?

700

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

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.

Firefox 145.0.2

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

16.0.1

Which version of Nextcloud? (if relevant)

32.0.2

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

No response

Describe the Bug

I'm getting the following error with any sync action (pull, push, merge)

E020: Could not parse server response. Content-Length header of network response exceeds response Body. | Last synchronized: 6 minutes ago

This happens with time based synchronisation and manually triggered syncs

I removed my existing profile and created a new one, but still get this issue.

Debug log (redacted):
floccus-5.8.2-2025-12-10-redacted.log

Expected Behavior

Floccus should sync bookmarks with Nextcloud

To Reproduce

Use Nextcloud for bookmarks
Attempt a sync

Debug log provided

I have provided a debug log file

Originally created by @exu-g on GitHub (Dec 10, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2117 ### Which version of floccus are you using? 5.8.2 ### How many bookmarks do you have, roughly? 700 ### 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. Firefox 145.0.2 ### Which version of Nextcloud Bookmarks are you using? (if relevant) 16.0.1 ### Which version of Nextcloud? (if relevant) 32.0.2 ### What kind of WebDAV server are you using? (if relevant) _No response_ ### Describe the Bug I'm getting the following error with any sync action (pull, push, merge) ``` E020: Could not parse server response. Content-Length header of network response exceeds response Body. | Last synchronized: 6 minutes ago ``` This happens with time based synchronisation and manually triggered syncs I removed my existing profile and created a new one, but still get this issue. Debug log (redacted): [floccus-5.8.2-2025-12-10-redacted.log](https://github.com/user-attachments/files/24084486/floccus-5.8.2-2025-12-10-redacted.log) ### Expected Behavior Floccus should sync bookmarks with Nextcloud ### To Reproduce 1. Use Nextcloud for bookmarks 2. Attempt a sync ### Debug log provided - [x] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Dec 10, 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 (Dec 10, 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:58 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 10, 2025):

Hello @exu-g
Thank you for taking the time to give feedback by opening this issue! Have you had floccus working with this Nextcloud server before and now it suddenly broke, or is this your first time trying out floccus? If this is your first time trying floccus, the error message would indicate that something is wrong with your nextcloud server configuration.

@marcelklehr commented on GitHub (Dec 10, 2025): Hello @exu-g Thank you for taking the time to give feedback by opening this issue! Have you had floccus working with this Nextcloud server before and now it suddenly broke, or is this your first time trying out floccus? If this is your first time trying floccus, the error message would indicate that something is wrong with your nextcloud server configuration.

kerem commented

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

Author

Owner

@exu-g commented on GitHub (Dec 10, 2025):

Sorry, 100% an issue with my server.
My reverse proxy had a full disk and turns out that causes all sorts of weird issues.
I freed up some space and sync works perfectly again
Thanks for your work on floccus, have a coffee (or something else) on me

@exu-g commented on GitHub (Dec 10, 2025): Sorry, 100% an issue with my server. My reverse proxy had a full disk and turns out that causes all sorts of weird issues. I freed up some space and sync works perfectly again Thanks for your work on floccus, have a coffee (or something else) on me

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Dec 10, 2025):

Yay, I'm glad it works. Thanks for your donation :)

@marcelklehr commented on GitHub (Dec 10, 2025): Yay, I'm glad it works. Thanks for your donation :)

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

No description provided.

Rows
Columns