Update Broke and Can't Fix

[Seventy-9DegreesNorth]

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

WebDAV

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

Edge, latest

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)

Synology NAS with https.

Describe the Bug

Have been using Floccus for a couple of years now. Have donated. Update broke my webdav connection and can't get it working -- not sure why. Log shows:
2025-12-22T20:41:56.245Z Starting sync process for account XXXBookmarks
2025-12-22T20:41:56.251Z onSyncStart: begin
2025-12-22T20:41:56.251Z https://MYDOMAIN.com:5006/bookmarks.xbel.lock
2025-12-22T20:41:56.274Z Setting lock: https://MYDOMAIN.com:5006/bookmarks.xbel.lock
2025-12-22T20:41:56.298Z Syncing failed with E019: HTTP status 405. Failed PUT request. Check your server configuration and log.
2025-12-22T20:41:56.298Z onSyncFail

Credentials work for server. Not sure what's happening. Again, worked great for 2 years untill recent update in beginning of DEcember.

Expected Behavior

That it would sync with same setup and credentials.

To Reproduce

N/A

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 @Seventy-9DegreesNorth
Thank you for taking the time to give feedback by opening this issue, and thank you for generously donating to this project!
HTTP status 405 would indicate that something is wrong with the URL, or maybe something changed on the server? In the last months I haven't touched the WebDAV implementation, so it surprises me that it would cause this issue. Can you try connecting to your webdav server with a different webdav client and try to upload a file in the root directory?

[Seventy-9DegreesNorth]

My apologies. I figured out the issue. When specifying the WEBDAV URL, I did not include the directory I was syncing to -- so -- since the permissions on the webdav server (Synology) are folder specific, and I only had a specific user (FloccusSync) as the user of that folder, when the Webdav tried to access the root folder, it of course didn't work.

Again, my apologies. It's hard to keep track of configurations for things and remember them when reconfiguring after an update that overwrites configurations. All good now.