mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 14:16:12 +03:00
[GH-ISSUE #2132] E019: HTTP status 405. Failed PUT request. (Linux on Firefox and Brave) #1432
Labels
No labels
browser-specific
bug
correctness issues
enhancement
feature: Google Drive
feature: Linkwarden
feature: git
feature: nextcloud-bookmarks
feature: tabs
feature: webdav
help wanted
native-app
priority: high
priority: low
priority: medium
pull-request
question
question
stale
upstream
waiting for more information
wontfix
🙁 Not following issue template
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/floccus#1432
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @rasp-pareses1 on GitHub (Dec 20, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2132
Which version of floccus are you using?
5.8.2
How many bookmarks do you have, roughly?
100
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.
Firefox and Brave
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)
Connecting from Linux (Kernel 6.17) to Synology WebDAV server.
Tried both Firefox 140.6.0 esr and Brave (Current), same error.
Floccus is working from macOS Brave to same WebDAV server.
Describe the Bug
E019: HTTP status 405. Failed PUT request. Check your server configuration and log. | Last synchronized: 0 seconds ago
Expected Behavior
Sync
To Reproduce
Install extension, server address and credentials.
Debug log provided
@github-actions[bot] commented on GitHub (Dec 20, 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! 💙
@rasp-pareses1 commented on GitHub (Dec 20, 2025):
Actually, the previous configured profile on macOS is working, but if a new profile is created on macOS same issue is experienced.
@rasp-pareses1 commented on GitHub (Dec 20, 2025):
Please delete - user error... :) Working fine now.
@marcelklehr commented on GitHub (Dec 20, 2025):
Anything I could make more obvious in the UI to prevent this kind of user error? :)
@rasp-pareses1 commented on GitHub (Dec 20, 2025):
Hi Marcel - awesome app, thanks so much for releasing it!
I was entering in the "Bookmarks file" path incorrectly. So perhaps you might like to consider adding that as a suggestion in the error message to be checked. E.g. Double check your bookmarks file path is entered correctly.
sharename/foldername/filename.xbel
Also, after that, I had another error and evenually discovered it was because my server was using https://hostname.server.com:5006 WebDAV and my browser didn't have my internal Root CA imported for that domain within the trusted CA section within the browser. After importing the Root CA certificate it connected sucessfully. This was on linux, as importing a Root CA in the OS doesn't import it to the browser, you need to import it seperately to each browser you're using. macOS doesn't have this issue, the browser references the keychain, so you only need to import it to the keychain and not seperately in the browser.