[Self-signed certificate; v5.x] E017: Network error about floccus HOT 11 OPEN

Is there any solution or do you recommend reinstalling version 4....?

from floccus.

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 💙

from floccus.

Good morning,
same problem, with two machines, one with Debian 11 and the other with Debian 12. Brave browser. Synchronization no longer works, error E017, after updating to version 5.0.10.

from floccus.

Good morning,
I don't know if it can help.
I tried version 5.0.10, with Firefox version 123.0.1 always with nextcloud, and it works well here.

from floccus.

Mh, I'm not sure what could have caused this, maybe manifest v3 is more strict when it comes to self-signed certs

from floccus.

I haven't had time to reproduce and investigate yet. Quick fix would certainly be to go back to v4.x but that will stop working some time in June/July when Google enforces manifest v3

from floccus.

I'll add my 2 cents in

Had the same E017 issue with a TrueNAS Core TrueNAS-13.0-U4 WebDav share

The cert on the server is from our an internal CA and is a wildcard cert on the TrueNAS system
Using Chrome to browse to the same URL 'https://kye-nas01:8081/Share01/' that the floccus profile uses, gave a certificate not valid message
changing the URL in Chrome to 'https://kye-nas01.kyetech.local:8081/Share01/' - chrome now sees it as a valid cert

in the floccus profile
the URL was https://kye-nas01:8081/Share01/

• which gave the E017 error

After changing the URL to https://kye-nas01.kyetech.local:8081/Share01/

• no more E017 error and the bookmarks.xbel file was created

I hope this helps with others

from floccus.

Is there any solution or do you recommend reinstalling version 4....?

Thanks @swirlypillow for posting this issue. I love Floccus but I too encountered the exact same issue and got very frustrated.

THE SOLUTION
I downgraded to Floccus v4.19.1 by uninstalling the current version and manually install the old version.
This works with my homelab installation of Nextcloud Self Signed Certificates on the latest versions of

• Chrome
• Brave Browser
• Vivaldi and
• Microsoft Edge

Message to @marcelklehr
May I suggest you run a poll to all your loyal Floccus users and gauge how many are using Self-signed vs purchased an SSL certificate?

I think you may be pleasantly surprised how many people are using "Self-signed" and will be impacted by Google's manifest 3 forced rollout come June/July as this will leave many stranded and frustrated with no work around.

However, if you were to come up with workaround with Nextcloud Bookmarks, that would be superb and would keep your loyal fans of Floccus happy. Just a thought.

from floccus.

Thank you for weighing in @mvozzo! I understand that this is frustrating. Unfortunately, I have no way to influence Chromium's (and derivatives) SSL/TLS behavior. If you know other addons that have transitioned to manifest v3 already and are working with self-signed certificates, I could perhaps take a leaf out of their book, but so far I see no option to fix this. I'm sorry. 😿

Update: This is filed in chrome's bug tracker already, so here's hoping it will be fixed soon :)

from floccus.

If you know other addons that have transitioned to manifest v3 already and are working with self-signed certificates,

Thanks for the reply @marcelklehr I have a followup question...
Out of curiosity (as I'm not a developer) does this mean those of us running homelab Nextcloud servers with Self-Signed Certificates are going to have issues (not just with Floccus) but with everything, once Google removes support for manifest v2?

from floccus.

does this mean those of us running homelab Nextcloud servers with Self-Signed Certificates are going to have issues (not just with Floccus) but with everything, once Google removes support for manifest v2?

Likely yes

from floccus.