E019: HTTP status 400. Failed POST request

[ali2key]

Which version of floccus are you using?

floccus-5.8.6

How many bookmarks do you have, roughly?

2500-3000

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

Brave Bookmarks Sync

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 1.88.132 (Official Build) (64-bit) Chromium: 146.0.7680.80

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

Getting such an error while syncing bookmarks:
E019: HTTP status 400. Failed POST request. Check your server configuration and log. | Last synchronized: 0 seconds ago

Expected Behavior

Succesfull sync, no errors

To Reproduce

Create the following sync profile:
[
{
"enabled": true,
"localRoot": "0",
"strategy": "default",
"syncInterval": 15,
"nestedSync": true,
"failsafe": true,
"allowNetwork": false,
"label": "LINKWARDEN",
"errorCount": 3635,
"clickCountEnabled": false,
"type": "linkwarden",
"url": "https://linkwarden.example.com",
"username": "root",
"password": "12332424242234242424",
"serverFolder": "Bookmarks",
"includeCredentials": false,
"allowRedirects": false,
"syncIntervalEnabled": true,
"syncing": false,
"scheduled": false,
"error": "E019: HTTP status 400. Failed POST request. Check your server configuration and log.",
"rootPath": "",
"isTransientError": false
}
]

floccus.export.json

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]

Hello @ali2key
Thank you for taking the time to give feedback by opening this issue! I'm sorry for the delay on my part.
Can you share the debug log from a sync run that fails like this? It would be interesting to see which exact request is failing. Also, do you know which Linkwarden version you are using? Do you have access to the server logs?

[ali2key]

Thanks for your work. I tried exporting the Floccus logs but the files are empty. See attached.

floccus-5.8.6-2026-03-29-full.log

I’m using Linkwarden v2.13.5. These are server logs from when I clicked “Sync now” in Floccus. Bookmarks are being added to Linkwarden, but Floccus is reporting errors.
[1] Restarting main browser (30-minute rotation)... [1] Restarting main browser (30-minute rotation)... [1] Processing 3 links for the following userId: 1 [1] - Link https://blog.askomputer.pl/jak-zrobic-tani-siem-w-firmie-zabbix-wazuh-zamiast-splunk/ for user 1 [1] - Link https://learn.microsoft.com/en-gb/security/zero-trust/assessment/get-started for user 1 [1] - Link https://www.reddit.com/r/Intune/comments/1s4kd9s/forcing_edge_as_the_only_browser_how_did_you/ for user 1 [0] Error: Fetch title timeout [0] at Timeout._onTimeout (/data/apps/web/.next/server/pages/api/v1/links.js:1:7323) [0] at listOnTimeout (node:internal/timers:581:17) [0] at process.processTimers (node:internal/timers:519:7) [1] Error: Fetch header timeout [1] at Timeout._onTimeout (/data/apps/worker/lib/fetchHeaders.ts:42:16) [1] at listOnTimeout (node:internal/timers:581:17) [1] at process.processTimers (node:internal/timers:519:7) [1] Error: Fetch header timeout [1] at Timeout._onTimeout (/data/apps/worker/lib/fetchHeaders.ts:42:16) [1] at listOnTimeout (node:internal/timers:581:17) [1] at process.processTimers (node:internal/timers:519:7) [1] Succeeded processing link https://learn.microsoft.com/en-gb/security/zero-trust/assessment/get-started for user 1. [1] Indexed 1 link, 0 left. [1] Failed Link: https://www.reddit.com/r/Intune/comments/1s4kd9s/forcing_edge_as_the_only_browser_how_did_you/ [1] Reason: page.goto: Timeout 30000ms exceeded. [1] Call log: [1] - navigating to "https://www.reddit.com/r/Intune/comments/1s4kd9s/forcing_edge_as_the_only_browser_how_did_you/", waiting until "domcontentloaded" [1] [1] at <anonymous> (/data/apps/worker/lib/archiveHandler.ts:121:22) [1] at async archiveHandler (/data/apps/worker/lib/archiveHandler.ts:102:5) [1] at async archiveLink (/data/apps/worker/workers/linkProcessing.ts:51:9) [1] at async linkProcessing (/data/apps/worker/workers/linkProcessing.ts:71:5) { [1] name: 'TimeoutError' [1] } [1] Error processing link https://www.reddit.com/r/Intune/comments/1s4kd9s/forcing_edge_as_the_only_browser_how_did_you/ for user 1: page.goto: Timeout 30000ms exceeded. [1] Call log: [1] - navigating to "https://www.reddit.com/r/Intune/comments/1s4kd9s/forcing_edge_as_the_only_browser_how_did_you/", waiting until "domcontentloaded" [1] [1] at <anonymous> (/data/apps/worker/lib/archiveHandler.ts:121:22) [1] at async archiveHandler (/data/apps/worker/lib/archiveHandler.ts:102:5) [1] at async archiveLink (/data/apps/worker/workers/linkProcessing.ts:51:9) [1] at async linkProcessing (/data/apps/worker/workers/linkProcessing.ts:71:5) { [1] name: 'TimeoutError' [1] } [1] Failed Link: https://blog.askomputer.pl/jak-zrobic-tani-siem-w-firmie-zabbix-wazuh-zamiast-splunk/ [1] Reason: page.goBack: Timeout 30000ms exceeded. [1] Call log: [1] - waiting for navigation until "load" [1] - navigated to "https://blog.askomputer.pl/jak-zrobic-tani-siem-w-firmie-zabbix-wazuh-zamiast-splunk/" [1] [1] at handleArchivePreview (/data/apps/worker/lib/preservationScheme/handleArchivePreview.ts:45:16) [1] at async <anonymous> (/data/apps/worker/lib/archiveHandler.ts:153:30) [1] at async archiveHandler (/data/apps/worker/lib/archiveHandler.ts:102:5) [1] at async archiveLink (/data/apps/worker/workers/linkProcessing.ts:51:9) [1] at async linkProcessing (/data/apps/worker/workers/linkProcessing.ts:71:5) { [1] name: 'TimeoutError' [1] } [1] Error processing link https://blog.askomputer.pl/jak-zrobic-tani-siem-w-firmie-zabbix-wazuh-zamiast-splunk/ for user 1: page.goBack: Timeout 30000ms exceeded. [1] Call log: [1] - waiting for navigation until "load" [1] - navigated to "https://blog.askomputer.pl/jak-zrobic-tani-siem-w-firmie-zabbix-wazuh-zamiast-splunk/" [1] [1] at handleArchivePreview (/data/apps/worker/lib/preservationScheme/handleArchivePreview.ts:45:16) [1] at async <anonymous> (/data/apps/worker/lib/archiveHandler.ts:153:30) [1] at async archiveHandler (/data/apps/worker/lib/archiveHandler.ts:102:5) [1] at async archiveLink (/data/apps/worker/workers/linkProcessing.ts:51:9) [1] at async linkProcessing (/data/apps/worker/workers/linkProcessing.ts:71:5) { [1] name: 'TimeoutError' [1] } [1] Processed 3 links, 1 left. [1] Indexed 2 links, 0 left. [1] Processing 1 link for the following userId: 1 [1] - Link https://www.reddit.com/r/microsoft365/comments/1s51l3c/i_ran_a_full_entra_id_security_assessment_in_15/ for user 1 [1] Error: Fetch header timeout [1] at Timeout._onTimeout (/data/apps/worker/lib/fetchHeaders.ts:42:16) [1] at listOnTimeout (node:internal/timers:581:17) [1] at process.processTimers (node:internal/timers:519:7) [1] Error: Could not parse CSS stylesheet [1] at exports.createStylesheet (/data/node_modules/jsdom/lib/jsdom/living/helpers/stylesheets.js:37:21) [1] at HTMLStyleElementImpl._updateAStyleBlock (/data/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:68:5) [1] at HTMLStyleElementImpl._poppedOffStackOfOpenElements (/data/node_modules/jsdom/lib/jsdom/living/nodes/HTMLStyleElement-impl.js:42:10) [1] at JSDOMParse5Adapter.onItemPop (/data/node_modules/jsdom/lib/jsdom/browser/parser/html.js:175:43) [1] at Parser.onItemPop (/data/node_modules/parse5/dist/cjs/parser/index.js:158:90) [1] at OpenElementStack.pop (/data/node_modules/parse5/dist/cjs/parser/open-element-stack.js:89:22) [1] at endTagInText (/data/node_modules/parse5/dist/cjs/parser/index.js:2287:20) [1] at Parser._endTagOutsideForeignContent (/data/node_modules/parse5/dist/cjs/parser/index.js:931:17) [1] at Parser.onEndTag (/data/node_modules/parse5/dist/cjs/parser/index.js:897:18)