mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 06:06:05 +03:00
[GH-ISSUE #2068] Cloudflare DDoS protection doesn't let floccus through: New bookmark has name "Just a moment..." #1384
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#1384
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 @eku on GitHub (Sep 21, 2025).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/2068
Which version of floccus are you using?
5.7.0
How many bookmarks do you have, roughly?
200
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.
Fennec 140
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)
No response
Describe the Bug
When sharing an URL from Fennect to Floccus the name of the bookmark is always "Just a moment...". URL is correct.
Expected Behavior
Name of site/url is taken over from the intend sent by the browser.
This worked in the past, but is currently broken.
To Reproduce
Share a URL from within the browser to floccus.
Debug log provided
@github-actions[bot] commented on GitHub (Sep 21, 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! 💙
@marcelklehr commented on GitHub (Sep 24, 2025):
Hey @eku
Thank you for taking the time to give feedback by opening this issue! I can not reproduce this with Fennec 143.0.2. It's very likely an issue in fenec and may have been fixed in recent versions. Can you try updating fennec?
@eku commented on GitHub (Dec 12, 2025):
Hi @marcelklehr
the bug is back again with 5.8.1 of this app.
@marcelklehr commented on GitHub (Dec 12, 2025):
Hi @eku
Thank you for the heads up. What fixed this issue last time? Is your Fennec up to date?
@eku commented on GitHub (Dec 12, 2025):
Hi Marcel,
if it worked with the installed version of Fennec and I only updated floccus, then I wouldn't suspect Fennec as the cause. What do you think?
@marcelklehr commented on GitHub (Dec 12, 2025):
mh, so last time it didn't work, then you updated floccus, then it worked again, now you updated floccus again and it doesn't work again? The thing is, I never changed anything in this functionality, neither then nor now, I believe.
@eku commented on GitHub (Dec 13, 2025):
I suspect that this concerns bookmarks for pages behind Cloudflare. The message seems very suspicious to me. Does Floccus check the link itself, or could it be that Fennec calls up the link again as part of the “Share link” action in order to refresh the page title?
Do you know of a way to log the contents of Fennec's intent to Floccus? I would like to find out whether Fennec already sends the “Just a moment” message.
@marcelklehr commented on GitHub (Dec 14, 2025):
Floccus checks the link on its own if the browser doesn't send a title. Debug logs are only enabled for dev builds. Maybe there's another App that can display the sent intent?
@eku commented on GitHub (Dec 18, 2025):
Looks like Fennec sends the URL only
https://hg-edge.mozilla.org/mozilla-central/file/tip/mobile/android/android-components/components/feature/contextmenu/src/main/java/mozilla/components/feature/contextmenu/ContextMenuCandidate.kt#l497
and Floccus does a request for the title in a form that causes Cloudflare to check the browser. That's not nice.
I'm not sure if this post gives any hint to what should be changed in Floccus.
@marcelklehr commented on GitHub (Dec 18, 2025):
I think these cloudflares checks always happen the first time you visit a site that is protected by cloudflare. There is no way around it. If the website send this page instead of the actual page, there is nothing floccus can do to figure out the correct title. Cloudflare is doing exactly what it advertises, it checks whether the thing on the other end is a human. Floccus will likely always have a hard time to tick that box, unfortunately. 😅
@eku commented on GitHub (Dec 19, 2025):
Would using Android's webview a possible solution to the problem?
@marcelklehr commented on GitHub (Dec 19, 2025):
The issue is not the user agent, but the captcha. We can load the website, perhaps, but you would still have to manually check the box, so the website has to be in the foreground and we have to somehow wait until the real page is displayed to get the real page title. This is not a good approach.