-
-
Notifications
You must be signed in to change notification settings - Fork 228
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Self-signed certificate; v5.x] E017: Network error #1560
Comments
Hello 👋 Thank you for taking the time to open this issue with floccus. I know it's frustrating when software I look forward to working with you on this issue |
Good morning, |
Good morning, |
Mh, I'm not sure what could have caused this, maybe manifest v3 is more strict when it comes to self-signed certs |
Is there any solution or do you recommend reinstalling version 4....? |
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 |
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 in the floccus profile
After changing the URL to https://kye-nas01.kyetech.local:8081/Share01/
I hope this helps with others |
Thanks @swirlypillow for posting this issue. I love Floccus but I too encountered the exact same issue and got very frustrated. THE SOLUTION
Message to @marcelklehr 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. |
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 :) |
Thanks for the reply @marcelklehr I have a followup question... |
Likely yes |
Is firefox likely to run into the same issue with self-signed certificates ? |
I don't know, I don't think so, for now. |
Which version of floccus are you using?
5.0.10
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.
Brave
Version 1.63.169 Chromium: 122.0.6261.111
Which version of Nextcloud Bookmarks are you using? (if relevant)
13.1.3
Which version of Nextcloud? (if relevant)
28.0.3
What kind of WebDAV server are you using? (if relevant)
No response
Describe the Bug
I get a "E017: Network error: Check your network connection and your account details" after upgrading to 5.0.10. I am using a Nextcloud instance hosted on my private network. The site is accessible over 443, and is using a self-signed certificate. The certificate is not expired, but the browser marks the site as not secure because it is self-signed. I'm not sure this is totally relevant, because with the last version of Floccus 4, this did not seem to matter. All I had to do was navigate to the Nextcloud site and accept the security warning, and everything worked fine. Now I get this error. I've tried deleting the profile and recreating it, which did not help.
Expected Behavior
I expected my bookmarks to continue to sync with Nextcloud Bookmarks as they have always done.
To Reproduce
Click the "sync now" button or click the "sync all profiles" button.
Debug log provided
I would but it generates a 0 byte file so there's nothing to attach.
The text was updated successfully, but these errors were encountered: