[GH-ISSUE #208] Option to accept Self Signed Certificates

kerem commented

2026-02-25 22:36:27 +03:00

Owner

Originally created by @giomf on GitHub (Dec 4, 2018).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/208

Software versions

Browser: Firefox 63.0.3
Nextcloud: 14.0.4.2
Nextcloud Bookmarks app: 0.14.2
Floccus: 3.1.14
Floccus sync method: nextcloud-folders

Steps to reproduce

Open Firefox (Private Mode)
Sync by clicking on "Sync now"

Expected outcome

Because Im in Private Mode, the self signed Certificates never gets saved.
A Dialog, that Im trying to connect to an "unsafe" webpage with an option to accept (Like Firefox normally does)

Actual outcome

"Network Error: Check your Connection or your account details"

Workaround

So as workaround I have to connect to my Server first, accept the untrusted Certificate and after that I can Sync via floccus

Originally created by @giomf on GitHub (Dec 4, 2018). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/208  ### Software versions  - Browser: Firefox 63.0.3 - Nextcloud: 14.0.4.2 - Nextcloud Bookmarks app: 0.14.2 - Floccus: 3.1.14 - Floccus sync method: nextcloud-folders  ### Steps to reproduce  1. Open Firefox (Private Mode) 2. Sync by clicking on "Sync now" ### Expected outcome  Because Im in Private Mode, the self signed Certificates never gets saved. A Dialog, that Im trying to connect to an "unsafe" webpage with an option to accept (Like Firefox normally does) ### Actual outcome  "Network Error: Check your Connection or your account details" ### Workaround So as workaround I have to connect to my Server first, accept the untrusted Certificate and after that I can Sync via floccus

kerem closed this issue

2026-02-25 22:36:27 +03:00

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 9, 2018):

Hey,

It should be possible to store a permanent exception for your self-signed certificate. This way you don't have to manually accept it every time. Let me know if that works.

@marcelklehr commented on GitHub (Dec 9, 2018): Hey, It should be possible to [store a permanent exception](https://www.attachmate.com/documentation/gateway-1-1/gateway-admin-guide/data/fxg_add_untrusted_cert.htm) for your self-signed certificate. This way you don't have to manually accept it every time. Let me know if that works.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@giomf commented on GitHub (Dec 9, 2018):

Hi,
as I mentioned, its not possible because I'm using Firefox in Private-mode. so no History neither Certificates are stored permanently. After every restart I have to accept it again.

@giomf commented on GitHub (Dec 9, 2018): Hi, as I mentioned, its not possible because I'm using Firefox in Private-mode. so no History neither Certificates are stored permanently. After every restart I have to accept it again.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 9, 2018):

I see. Is it possible to disable private mode temporarily and then add the exception permanently?

@marcelklehr commented on GitHub (Dec 9, 2018): I see. Is it possible to disable private mode temporarily and then add the exception permanently?

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@giomf commented on GitHub (Dec 9, 2018):

Yes that's possible.
But I would appreciate to have this feature.

@giomf commented on GitHub (Dec 9, 2018): Yes that's possible. But I would appreciate to have this feature.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@marcelklehr commented on GitHub (Dec 9, 2018):

Unfortunately, I don't think it's possible to reach that deeply into the security architecture with an extension. It's also kind of out of scope for floccus to handle this. In a time of let's encyrpt availability, I would simply suggest to use them as a CA and avoid self-signed certificates, if possible.

@marcelklehr commented on GitHub (Dec 9, 2018): Unfortunately, I don't think it's possible to reach that deeply into the security architecture with an extension. It's also kind of out of scope for floccus to handle this. In a time of let's encyrpt availability, I would simply suggest to use them as a CA and avoid self-signed certificates, if possible.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@giomf commented on GitHub (Dec 9, 2018):

Ok I see,
Unfortunately, Im dealing with some kind of dyndns. so no Let's Encrypt for me...
Thank you anyway

@giomf commented on GitHub (Dec 9, 2018): Ok I see, Unfortunately, Im dealing with some kind of dyndns. so no Let's Encrypt for me... Thank you anyway

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@mnalis commented on GitHub (Dec 17, 2018):

Just to note that Let's Encrypt works just fine with dynamic IPs (like in dyndns) for me.

All it requires is that your hostname resolves to correct IP at the moment of renewal, so LE servers can connect to your LE script. So, if your machine HTTPS can be directly reached on the Internet (without using VPNs or similar hacks), you can use Let's Encrpyt to provide its certificates.
Hopefully it helps the OP.

@mnalis commented on GitHub (Dec 17, 2018): Just to note that Let's Encrypt works just fine with dynamic IPs (like in dyndns) for me. All it requires is that your hostname resolves to correct IP at the moment of renewal, so LE servers can connect to your LE script. So, if your machine HTTPS can be directly reached on the Internet (without using VPNs or similar hacks), you can use Let's Encrpyt to provide its certificates. Hopefully it helps the OP.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@bernd-wechner commented on GitHub (Dec 17, 2018):

I can second mnalis, and state that I use letsencrypt to maintain certs for at least two servers behind a single router (gateway) that has a dynamic names (ddns). Yes, plural. Multiple domain names pointing to one dynamic IP address at which my gateway farms incoming traffic out to a machine on my LAN based on the domain name used. And the names are managed just fine with letsencrypt.

@bernd-wechner commented on GitHub (Dec 17, 2018): I can second mnalis, and state that I use letsencrypt to maintain certs for at least two servers behind a single router (gateway) that has a dynamic names (ddns). Yes, plural. Multiple domain names pointing to one dynamic IP address at which my gateway farms incoming traffic out to a machine on my LAN based on the domain name used. And the names are managed just fine with letsencrypt.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@giomf commented on GitHub (Dec 30, 2018):

Thanks,
I will give it a try

@giomf commented on GitHub (Dec 30, 2018): Thanks, I will give it a try

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 12, 2022):

Adding android user level certs does not seem to work for everyone.

@marcelklehr commented on GitHub (Apr 12, 2022): Adding android user level certs does not seem to work for everyone.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 12, 2022):

Oops, wrong issue. Sorry.

@marcelklehr commented on GitHub (Apr 12, 2022): Oops, wrong issue. Sorry.

kerem commented

2026-02-25 22:36:28 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 13, 2023):

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 (Apr 13, 2023): 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 22:36:29 +03:00

[GH-ISSUE #215] Chromium Brave: Folder #-1[undefined] contains an nonexistent bookmark 19875 #206

kerem referenced this issue

2026-02-25 22:36:29 +03:00

[GH-ISSUE #215] Chromium Brave: Folder #-1[undefined] contains an nonexistent bookmark 19875 #206