starred/floccus

Fork 0

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

[GH-ISSUE #1991] E019: HTTP status 404. Failed PUT request. Check your server configuration and log #1333

New issue

Closed

opened 2026-02-25 22:39:43 +03:00 by kerem · 3 comments

kerem commented

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

Owner

Originally created by @cler1818 on GitHub (Jul 15, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1991

Which version of floccus are you using?

5.4.5

How many bookmarks do you have, roughly?

200

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

Sync method

WebDAV

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

Chromium 118.0.5993.159/138.0.7204.101

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

Which version of Nextcloud? (if relevant)

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

坚果云
https://dav.jianguoyun.com/dav/

Describe the Bug

E019: HTTP status 404. Failed PUT request. Check your server configuration and log. | 上次同步: 0 seconds 之前

DEBUG：
2025-07-15T09:36:28.198Z Starting sync process for account 浏览器书签
2025-07-15T09:36:28.201Z onSyncStart: begin
2025-07-15T09:36:28.202Z https://dav.jianguoyun.com/dav/bookmarks.xbel.lock
2025-07-15T09:36:28.292Z Setting lock: https://dav.jianguoyun.com/dav/bookmarks.xbel.lock
2025-07-15T09:36:28.361Z Syncing failed with E019: HTTP status 404. Failed PUT request. Check your server configuration and log.
2025-07-15T09:36:28.366Z onSyncFail

Expected Behavior

2025-07-15T09:36:28.198Z Starting sync process for account 浏览器书签
2025-07-15T09:36:28.201Z onSyncStart: begin
2025-07-15T09:36:28.202Z https://dav.jianguoyun.com/dav/bookmarks.xbel.lock
2025-07-15T09:36:28.292Z Setting lock: https://dav.jianguoyun.com/dav/bookmarks.xbel.lock
2025-07-15T09:36:28.361Z Syncing failed with E019: HTTP status 404. Failed PUT request. Check your server configuration and log.
2025-07-15T09:36:28.366Z onSyncFail

To Reproduce

Debug log provided

I have provided a debug log file

Originally created by @cler1818 on GitHub (Jul 15, 2025). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1991 ### Which version of floccus are you using? 5.4.5 ### How many bookmarks do you have, roughly? 200 ### Are you using other means to sync bookmarks in parallel to floccus? NO ### Sync method WebDAV ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Chromium 118.0.5993.159/138.0.7204.101 ### Which version of Nextcloud Bookmarks are you using? (if relevant) NO ### Which version of Nextcloud? (if relevant) NO ### What kind of WebDAV server are you using? (if relevant) 坚果云 https://dav.jianguoyun.com/dav/ ### Describe the Bug E019: HTTP status 404. Failed PUT request. Check your server configuration and log. | 上次同步: 0 seconds 之前 DEBUG： 2025-07-15T09:36:28.198Z Starting sync process for account 浏览器书签 2025-07-15T09:36:28.201Z onSyncStart: begin 2025-07-15T09:36:28.202Z https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.292Z Setting lock: https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.361Z Syncing failed with E019: HTTP status 404. Failed PUT request. Check your server configuration and log. 2025-07-15T09:36:28.366Z onSyncFail ### Expected Behavior 2025-07-15T09:36:28.198Z Starting sync process for account 浏览器书签 2025-07-15T09:36:28.201Z onSyncStart: begin 2025-07-15T09:36:28.202Z https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.292Z Setting lock: https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.361Z Syncing failed with E019: HTTP status 404. Failed PUT request. Check your server configuration and log. 2025-07-15T09:36:28.366Z onSyncFail ### To Reproduce 2025-07-15T09:36:28.198Z Starting sync process for account 浏览器书签 2025-07-15T09:36:28.201Z onSyncStart: begin 2025-07-15T09:36:28.202Z https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.292Z Setting lock: https://dav.jianguoyun.com/dav/bookmarks.xbel.lock 2025-07-15T09:36:28.361Z Syncing failed with E019: HTTP status 404. Failed PUT request. Check your server configuration and log. 2025-07-15T09:36:28.366Z onSyncFail ### Debug log provided - [x] I have provided a debug log file

kerem

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

closed this issue
added the
bug
label

kerem commented

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

Author

Owner

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

Author

Owner

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

Hi @cler1818

Thank you for taking the time to give feedback by opening this issue! When using floccus with jianguoyun, you first need to make sure you have an app password and then make sure you are syncing the xbel file to a sub directory of dav.jianguoyun.com/dav -- for some reason no files can be stored in the root directory in nutstore.

@marcelklehr commented on GitHub (Jul 15, 2025): Hi @cler1818 Thank you for taking the time to give feedback by opening this issue! When using floccus with jianguoyun, you first need to make sure you [have an app password](https://www.jianguoyun.com/d/account#safe) and then make sure you are syncing the xbel file to a sub directory of [dav.jianguoyun.com/dav](https://dav.jianguoyun.com/dav/) -- for some reason no files can be stored in the root directory in nutstore.

kerem commented

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

Author

Owner

@cler1818 commented on GitHub (Jul 16, 2025):

Hi @cler1818

Thank you for taking the time to give feedback by opening this issue! When using floccus with jianguoyun, you first need to make sure you have an app password and then make sure you are syncing the xbel file to a sub directory of dav.jianguoyun.com/dav -- for some reason no files can be stored in the root directory in nutstore.

Thanks, perfect solution to the problem
Just enter https://dav.jianguoyun.com/dav/Floccus directly at the server address, that is, create a Floccus folder yourself, and cannot be created directly to the root directory.

@cler1818 commented on GitHub (Jul 16, 2025): > Hi [@cler1818](https://github.com/cler1818) > > Thank you for taking the time to give feedback by opening this issue! When using floccus with jianguoyun, you first need to make sure you [have an app password](https://www.jianguoyun.com/d/account#safe) and then make sure you are syncing the xbel file to a sub directory of [dav.jianguoyun.com/dav](https://dav.jianguoyun.com/dav/) -- for some reason no files can be stored in the root directory in nutstore. Thanks, perfect solution to the problem Just enter https://dav.jianguoyun.com/dav/Floccus directly at the server address, that is, create a Floccus folder yourself, and cannot be created directly to the root directory.

kerem referenced this issue

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

[PR #1333] [CLOSED] Bump intl-messageformat from 9.13.0 to 10.2.6 #1863

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

No description provided.

Rows
Columns