mirror of
https://github.com/floccusaddon/floccus.git
synced 2026-04-25 22:26:06 +03:00
[GH-ISSUE #1590] iOS app with Nextcloud self signed certificate #1050
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#1050
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 @banjoman05 on GitHub (May 6, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1590
Which version of floccus are you using?
latest iOS app
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.
iPadOS 17.4.1, iPad Pro 11 inch third gen
Which version of Nextcloud Bookmarks are you using? (if relevant)
v13.1.3
Which version of Nextcloud? (if relevant)
v29.0.0
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
Installed iOS app from app store on iPad. When inputting Nextcloud URL, a message is displayed and you are not allowed to skip/allow/ignore/etc...
"The certificate for this server is invalid. You might be connecting to a server that is pretending to be "[IP ADDRESS]" which could put your confidential information at risk."
This Nextcloud instance is already in use on desktop Firefox Addon and I was able to bypass any certificate issues.
Expected Behavior
Ability to ignore error, as this is expected behavior when using self-signed certificates on internal networks.
To Reproduce
Attempt to connect to Nextcloud with a self-signed certificate in the iOS app.
Debug log provided
@github-actions[bot] commented on GitHub (May 6, 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 (May 9, 2024):
Hi @banjoman05
This is a known issue that is hard to fix, because I don't want to simply ignore SSL errors for security reasons. For now Android and iOS versions of floccus cannot sync with a self-signed certificate.
@github-actions[bot] commented on GitHub (May 10, 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.