mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-26 14:45:59 +03:00
[GH-ISSUE #1511] E033: Redirect detected. #997
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#997
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 @eleaner on GitHub (Jan 5, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1511
Which version of floccus are you using?
5.0.7
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 121.0
Which version of Nextcloud Bookmarks are you using? (if relevant)
13.1.3
Which version of Nextcloud? (if relevant)
Nextcloud AIO v7.9.0
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
i created a profile and linked with the nextcloud account but I am receiving this error
attaching log
floccus-5.0.7-2024-01-05-full.log
I don't do any redirects that I am aware of
I found the option to ignore redirects but it does not help
and a second log
floccus-5.0.7-2024-01-05-full(1).log
Expected Behavior
synchronisation
To Reproduce
I am not sure, but i get the same error with brave
Debug log provided
@github-actions[bot] commented on GitHub (Jan 5, 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 and have been 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!
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 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 💙
@marcelklehr commented on GitHub (Jan 5, 2024):
Hi @eleaner
If you get a parse error, check the nextcloud log on your server
@eleaner commented on GitHub (Jan 5, 2024):
I see, my nextcloud is behind authelia
I believe floccs might be trying to connect from unauthorised session and gets rejected
@marcelklehr commented on GitHub (Jan 5, 2024):
mmmh, I've heard before that floccus doesn't seem to work well with authelia. I know very little about it, though. Do you know how floccus would need to behave to work with authelia?
@eleaner commented on GitHub (Jan 5, 2024):
I know very little too but if the session is authorised everything should work
e.g. when I authorise floccus to work with nextcloud - it uses my current session and authelia naturally let it pass.
so synchronisation should do the same but it seems to be establishing a new session or connect from a different server
@eleaner commented on GitHub (Jan 5, 2024):
by the way, disabling authelia made it work immediately - so that's definitely it
@marcelklehr commented on GitHub (Jan 5, 2024):
Mh. Floccus doesn't use sessions, though. You can try enabling "send client credentials" in the profile options, but out of the box, floccus only does HTTP basic auth.
@eleaner commented on GitHub (Jan 5, 2024):
well, I am not sure if "session" is a good term
what I mean is when i login to nextcloud it goes through authelia first
I actually don't have them integrated so next I have to login to nextcloud
but authorisation is remembered in the browser somehow
so even if I log-off nextcloud and try to login again, authelia will let me through
it will also let me through through every service that sits behind her
so i would say - browser is authorised
somehow authorisation of plugin in nextcloud also gets through authelia without any issue - still because browser is authorised
but then synchronisation in the same browser must do something different
I doubt I can explain it more clearly
@marcelklehr commented on GitHub (Jan 5, 2024):
From your explanation, it seems like authelia sets a cookie. Do you have other client software working with this setup? Like nextcloud desktop?
@eleaner commented on GitHub (Jan 5, 2024):
not that I am aware of
but I guess it would not work that easily as it would have to first allow authelia login
@marcelklehr commented on GitHub (Jan 7, 2024):
Have you tried the "send client credentials" in the profile options already? That might fix this, but other than that, I can not help you further.
@github-actions[bot] commented on GitHub (Jan 7, 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.