-
-
Notifications
You must be signed in to change notification settings - Fork 251
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
HTTP Error: 404 Not Found #1759
Comments
Hello 👋 Thank you for taking the time to open this issue with floccus. I know it's frustrating when software 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, I look forward to working with you on this issue |
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. |
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 |
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. |
I have no idea, to be honest. Floccus uses git over https to sync with gitea using https://isomorphic-git.org/ |
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
The text was updated successfully, but these errors were encountered: