starred/floccus

Fork 0

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

[GH-ISSUE #1531] Error with Koofr webdav +floccus android #1007

New issue

Closed

opened 2026-02-25 22:38:42 +03:00 by kerem · 3 comments

kerem commented

2026-02-25 22:38:42 +03:00

Owner

Originally created by @msalini on GitHub (Jan 27, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1531

Which version of floccus are you using?

5.0.9

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.

Lineage 18.1 (rooted) on Samsung Galaxy A5

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)

Koofr Webdav server

Describe the Bug

When syncing the file, i get the following error message:

E019: HTTP status 404. Failed PUT request. Check your server configuration and log.

steps to mitigate the error but didn't work

clean cache
change koofr sync folder
uninstall / reinstall the app
started with an empty folder and sync the entire bookmark again

Expected Behavior

Webdav should work

To Reproduce

Set up a new koofr webdav connection on the app and sync. Either with existing or new ptofile. Sync and error appears.

Debug log provided

I have provided a debug log file

Originally created by @msalini on GitHub (Jan 27, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1531 ### Which version of floccus are you using? 5.0.9 ### 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. Lineage 18.1 (rooted) on Samsung Galaxy A5 ### 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) Koofr Webdav server ### Describe the Bug When syncing the file, i get the following error message: `E019: HTTP status 404. Failed PUT request. Check your server configuration and log.` ### steps to mitigate the error but didn't work - clean cache - change koofr sync folder - uninstall / reinstall the app - started with an empty folder and sync the entire bookmark again ### Expected Behavior Webdav should work ### To Reproduce Set up a new koofr webdav connection on the app and sync. Either with existing or new ptofile. Sync and error appears. ### Debug log provided - [ ] I have provided a debug log file

kerem

2026-02-25 22:38:42 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-25 22:38:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Jan 27, 2024):

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.
I'm Marcel and I created floccus and have been maintaining it ever 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.
Note also that GitHub 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!
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 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.

I look forward to working with you on this issue
Cheers 💙

@github-actions[bot] commented on GitHub (Jan 27, 2024): 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. I'm Marcel and I created floccus and have been maintaining it ever 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. Note also that GitHub 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! 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 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. I look forward to working with you on this issue Cheers :blue_heart:

kerem commented

2026-02-25 22:38:42 +03:00

Author

Owner

@msalini commented on GitHub (Feb 5, 2024):

My fault, not a bug. A hard-to-detect typo in my folder path. Closing issue.

@msalini commented on GitHub (Feb 5, 2024): My fault, not a bug. A hard-to-detect typo in my folder path. Closing issue.

kerem commented

2026-02-25 22:38:42 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Feb 5, 2025):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Feb 5, 2025): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

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

No description provided.

Rows
Columns