Server responded with 405 E019: HTTP status

[PE5TT]

Which version of floccus are you using?

V5.8.6

How many bookmarks do you have, roughly?

~100

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

No

Sync method

Nextcloud Bookmarks

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

Firefox 148.0 for Linux Mint

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

V16.1.3

Which version of Nextcloud? (if relevant)

V32.0.6

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

No response

Describe the Bug

Floccus log
2026-03-11T10:12:01.458Z GET https://server.com/nextcloud/index.php/apps/bookmarks/public/rest/v2/folder/-1/children?layers=-1: Server responded with 405:
2026-03-11T10:12:01.459Z Syncing failed with E019: HTTP status 405. Failed GET request. Check your server configuration and log.

Apache log
192.168.1.2 - - [11/Mar/2026:12:55:13 +0100] "GET /nextcloud/index.php/apps/bookmarks/public/rest/v2/folder/-1/children?layers=-1 HTTP/1.1" 405 1561 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0"
192.168.1.2 - - [11/Mar/2026:12:55:13 +0100] "DELETE /nextcloud/index.php/apps/bookmarks/public/rest/v2/lock HTTP/1.1" 405 1569 "-" "Mozilla/5.0 (X11; Linux x86_64; rv:148.0) Gecko/20100101 Firefox/148.0"

Expected Behavior

My Phone is syncing just fine

Apache log phone sync
192.168.1.3 - - [11/Mar/2026:12:56:35 +0100"GET /nextcloud/index.php/apps/bookmarks/public/rest/v2/folder/9/children?layers=1 HTTP/1.1" 200 2401 "-" "Dalvik/2.1.0 (Linux; U; Android 16; Pixel 7 Build/BP2A.250805.005)"

To Reproduce

Tried to reinstall floccus and reconfigure, but did not fix it

The difference in the two GET requests from computer en phone is the /-1/ in the request resulting in the 405. On my phone this is /9/

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]

Hey @PE5TT
Thank you for taking the time to give feedback by opening this issue!
HTTP status 405 could indicate that the bookmarks app is not installed. So, on your phone this works and on your desktop it doesn't? Do they really sync to the same server?

[joshqou]

@marcelklehr I'm having the same issue on both macOS ungoogled chromium and Linux ungoogled chromium. The floccus iOS app works just fine. This only started happening after I updated my Nextcloud server and bookmarks app, maybe the API has changed in some way?

I have tried recreating my profiles, however the same behaviour remains.

Nextcloud 32.0.6, Bookmarks 16.1.3, Ungoogled Chromium (linux flatpak) 146.0.7680.80, Ungoogled Chromium (macOS) 146.0.7680.80, Floccus (linux chrome) 5.8.6, Floccus (macOS chrome) 5.8.0, Floccus (iOS) 5.8.6

[joshqou]

Potential clue: Loading the bookmarks app as /apps/bookmarks/ works fine whereas /index.php/apps/bookmarks/ results in a 404 when requesting /index.php/apps/bookmarks/bookmarks-service-worker.js. I have a feeling that stripping /index.php from the api calls would likely fix this issue (red herring)

[joshqou]

Looking at devtools shows the successful requests using a different authorization header to the failing (405) requests. Floccus can reach the endpoints from the /index.php prefix when using basic authentication but is then sending incorrect bearer tokens on subsequent requests, which are returning 405 instead of 401 for some reason.

Nextcloud isn't respecting the tickets that it's telling Floccus to use.

Manually replacing the invalid authorization header with the valid basic authorization header fixes the requests.

[marcelklehr]

Mmmh, interesting! Is this only happening with the children endpoint? I'm not seeing any 405 errors in my error dashboard on sentry, interstingly, so it seems to me that not many people are hitting this for some reason

[joshqou]

Seems like Nextcloud is completely ignoring the bearer tokens and treating them as invalid. The children and lock endpoints both behave like this

[marcelklehr]

But why is the phone syncing fine then? And why are there not more reports / can't I reproduce this?

[marcelklehr]

Is there anything in the nextcloud logs when these requests are happening both when they fail and when not?

[joshqou]

Running occ log:watch gives the following log every time floccus tries to sync, but that's it. Floccus mobile also generates these messages so I'm assuming the lock call is responsible since both the mobile app and extension can successfully hit it. No errors thrown by php.

  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:46+00:00 
  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:48+00:00 
  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:50+00:00 
  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:49+00:00 
  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:50+00:00 
  Info     no app in context  The user config key files/quota is not defined in the config lexicon                     2026-03-21T11:40:52+00:00 

But why is the phone syncing fine then? And why are there not more reports / can't I reproduce this?

Perhaps something to do with each of our installs? My nextcloud install is a few years old, iirc originally was Nextcloud 29. The database is MariaDB 10.11.15, PHP 8.4.16, and nginx 1.28.1.

An important thing I'll restate is that this only started happening after I upgraded from Nextcloud 30 to Nextcloud 32