starred/floccus

Fork 0

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

[GH-ISSUE #1759] HTTP Error: 404 Not Found #1175

New issue

Closed

opened 2026-02-25 22:39:13 +03:00 by kerem · 7 comments

kerem commented

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

Owner

Originally created by @Hr46ph on GitHub (Nov 7, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1759

Which version of floccus are you using?

5.3.1

How many bookmarks do you have, roughly?

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

Sync method

Git

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

Version 127.0.6533.119 (Official Build, ungoogled-chromium) (arm64)

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

n/a

Which version of Nextcloud? (if relevant)

n/a

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

n/a

Describe the Bug

I run a private Gitea server on Kubernetes. I created an account for floccus, created a repo and use the details in Floccus.
Floccus works and syncs fine.

When I login with my own account via Gitea web, Floccus stops working and gives error 404.

Expected Behavior

Floccus should work independently from my browser session.

I tried sending credentials but that doesn't change and fails the same.

To Reproduce

Create a separate account on gitea. I presume this will also work with gitlab and github but I didn't test.
Do NOT enable 2FA, just password authentication.
Login with the new account, and create a personal repository.
Setup Floccus to use the new account and repository.
Click sync, verify it works.

Open a tab, login to Gitea web with another account (not your new floccus account). Click Floccus addon, force sync. it will fail.

Debug log provided

I have provided a debug log file

Originally created by @Hr46ph on GitHub (Nov 7, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1759 ### Which version of floccus are you using? 5.3.1 ### How many bookmarks do you have, roughly? 1k ### Are you using other means to sync bookmarks in parallel to floccus? No ### Sync method Git ### Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please. Version 127.0.6533.119 (Official Build, ungoogled-chromium) (arm64) ### Which version of Nextcloud Bookmarks are you using? (if relevant) n/a ### Which version of Nextcloud? (if relevant) n/a ### What kind of WebDAV server are you using? (if relevant) n/a ### Describe the Bug I run a private Gitea server on Kubernetes. I created an account for floccus, created a repo and use the details in Floccus. Floccus works and syncs fine. When I login with my own account via Gitea web, Floccus stops working and gives error 404. ### Expected Behavior Floccus should work independently from my browser session. I tried sending credentials but that doesn't change and fails the same. ### To Reproduce Create a separate account on gitea. I presume this will also work with gitlab and github but I didn't test. Do NOT enable 2FA, just password authentication. Login with the new account, and create a personal repository. Setup Floccus to use the new account and repository. Click sync, verify it works. Open a tab, login to Gitea web with another account (not your new floccus account). Click Floccus addon, force sync. it will fail. ### Debug log provided - [ ] I have provided a debug log file

kerem

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

closed this issue
added the
bug

waiting for more information
labels

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 7, 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 a few years ago, 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
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.

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

@github-actions[bot] commented on GitHub (Nov 7, 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 a few years ago, 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! To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket, 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. I look forward to working with you on this issue Cheers :blue_heart:

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Nov 10, 2024):

Would be interesting to know which browser this is, as by default floccus shouldn't share cookies with the main browser session. Do you have perhaps enabled "send client credentials" in your profile settings?

@marcelklehr commented on GitHub (Nov 10, 2024): Would be interesting to know which browser this is, as by default floccus shouldn't share cookies with the main browser session. Do you have perhaps enabled "send client credentials" in your profile settings?

kerem commented

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

Author

Owner

@Hr46ph commented on GitHub (Nov 11, 2024):

Would be interesting to know which browser this is, as by default floccus shouldn't share cookies with the main browser session. Do you have perhaps enabled "send client credentials" in your profile settings?

Version 127.0.6533.119 (Official Build, ungoogled-chromium) (arm64)

Fully up to date MacOS Sequoia 15.1 on Apple Silicon.

When I noticed and investigated I enabled send client credentials to test it but it didn’t matter.

I think if it would share cookies with the main session refreshing the main browser page would log me in with Floccus after configuring Floccus and successfully sync. That does not happen the main browser session stays logged in with my own credentials it’s just floccus who seems to loose the login.

@Hr46ph commented on GitHub (Nov 11, 2024): > Would be interesting to know which browser this is, as by default floccus shouldn't share cookies with the main browser session. Do you have perhaps enabled "send client credentials" in your profile settings? Version 127.0.6533.119 (Official Build, ungoogled-chromium) (arm64) Fully up to date MacOS Sequoia 15.1 on Apple Silicon. When I noticed and investigated I enabled send client credentials to test it but it didn’t matter. I think if it would share cookies with the main session refreshing the main browser page would log me in with Floccus after configuring Floccus and successfully sync. That does not happen the main browser session stays logged in with my own credentials it’s just floccus who seems to loose the login.

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Nov 13, 2024):

huh. Can you reproduce this with another browser? I suspect this might be a bug in Ungoogled Chromium or Gitea otherwise, as I've never seen this

@marcelklehr commented on GitHub (Nov 13, 2024): huh. Can you reproduce this with another browser? I suspect this might be a bug in Ungoogled Chromium or Gitea otherwise, as I've never seen this

kerem commented

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

Author

Owner

@Hr46ph commented on GitHub (Nov 13, 2024):

It might be. I never considered it could be the website being the cause.

I tested it with a temporary account on Gitlab in Ungoogled Chromium and that works fine.

I then tested official Google Chrome with both Gitlab and my own Gitea and Gitlab works fine, Gitea logs Floccus out as well.

Its really weird. It seems its not the Floccus addon but if you have any idea about what could cause this, it would help me logging this bug with the Gitea developers.

@Hr46ph commented on GitHub (Nov 13, 2024): It might be. I never considered it could be the website being the cause. I tested it with a temporary account on Gitlab in Ungoogled Chromium and that works fine. I then tested official Google Chrome with both Gitlab and my own Gitea and Gitlab works fine, Gitea logs Floccus out as well. Its really weird. It seems its not the Floccus addon but if you have any idea about what could cause this, it would help me logging this bug with the Gitea developers.

kerem commented

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

Author

Owner

@marcelklehr commented on GitHub (Nov 13, 2024):

I have no idea, to be honest. Floccus uses git over https to sync with gitea using https://isomorphic-git.org/

@marcelklehr commented on GitHub (Nov 13, 2024): I have no idea, to be honest. Floccus uses git over https to sync with gitea using https://isomorphic-git.org/

kerem commented

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

Author

Owner

@github-actions[bot] commented on GitHub (Nov 14, 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 (Nov 14, 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.

kerem referenced this issue

2026-02-25 23:30:57 +03:00

[PR #1175] [MERGED] docs: add Seirade as a contributor for ideas, bug #1825

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

No description provided.

Rows
Columns