Floccus does not sync anymore since v5.4.0 -- Self-signed certificate?

[hochl]

Which version of floccus are you using?

5.4.0

How many bookmarks do you have, roughly?

500

Are you using other means to sync bookmarks in parallel to floccus?

No

Sync method

WebDAV

Which browser are you using? In case you are using the phone App, specify the Android or iOS version and device please.

Firefox on Linux and Windows 10/11.

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)

rclone

Describe the Bug

Everything worked flawlessly, floccus version V5.3.4 following the information window. Now none of my 5 Browser installs sync anymore, version installed is V5.4.0.

Expected Behavior

Obviously, all browsers should sync. The sync does not finish, thus i cannot export a debug log. On Linux I got an error message yesterday that said something with E030.

To Reproduce

Upgrade to V5.4.0 and you are hosed.

Debug log provided

• I have provided a debug log file

[github-actions]

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 a few years ago, 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!
To continue the development and maintenance of this project in a sustainable way it is expected that you donate to the project when opening a ticket,
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.

I look forward to working with you on this issue
Cheers 💙

[developer91234]

Can confirm. I've never tried this extension before but in my setup with webdav it won't sync anything despite not reporting any errors. I have two browsers, each with a bookmarks folder named flocus. The first one contains some bookmarks, the second is empty. No matter how many times I sync, or how much I fiddle with the sync settings, the second remains empty: nothing is synced to the second browser.

[marcelklehr]

Hello,

Thank you for reaching out. I can not reproduce this offhand, sadly. Can you perhaps share a screenshot?

[hochl]

floccus-5.4.0-2024-12-04-full.log

I swear the error number has changed, it now says E017, so maybe this is a different error \o/ Funny enough, one of my Linux machines now syncs again. Could this be some problem with SSL certificates? Because on two of my machines, there is a firewall that intercepts traffic and inserts its own certificate :(

[marcelklehr]

Yeah, network error is unlikely to be a problem in floccus.

[qlifee]

I have the same issue with the same error code E017 on:

1. Pixel 9 Android 15 (graphene os) Floccus 5.3.4.
   Surface running both
2. Linux Mint chromium browser Floccus 5.4.0 and
3. windows 11 running chrome browser Floccus 5.4.0.

This is my first time using Floccus and i didn't manage to get it to work.

I have WEBDAV server up and running on my Synology NAS, and i verified that it is working alright with various applications.

I suspect the problem is that Floccus doesn't allow self-signed certificates (No option to allow that), because the applications that didn't work are the ones that doesn't allow the self-signed certificates.

my WebDAV URL is https://<tailscale-ip-address>:<port>/Bookmarks
File format: XBEL

Note: I use tailscale to access my NAS.

[marcelklehr]

self-signed certificates

Yes, that's a problem. In the browser you can accept the certificate manually, but on android there's currently no way to import the cert in a way that will make floccus sync, sadly.

[qlifee]

In the browser you can accept the certificate manually.

I didn't get prompted to accept a certificate, how can i do that?

[marcelklehr]

I didn't get prompted to accept a certificate, how can i do that?

You can try accessing the webdav endpoint manually in a browser tab to get the prompt.

[qlifee]

You can try accessing the webdav endpoint manually in a browser tab to get the prompt.

Unfortunately it didn't work, however I managed to get it working on Firefox floccus 5.4.0.

So it might be a problem with chromium based browsers (Chromium, Chrome, Brave).

[hochl]

You can try accessing the webdav endpoint manually in a browser tab to get the prompt.

Unfortunately it didn't work, however I managed to get it working on Firefox floccus 5.4.0.

So it might be a problem with chromium based browsers (Chromium, Chrome, Brave).

I have not been able to sync floccus on any of my Chrome based browsers yet. Maybe my issues are related to me using rclone as WebDav server?

[marcelklehr]

I have not been able to sync floccus on any of my Chrome based browsers yet.

Error message or it didn't happen :)

If it's a network error, you can try connecting to rclone via a different webdav server and check if that works.

[qlifee]

I have the same issue with the same error code E017 on:

1. Pixel 9 Android 15 (graphene os) Floccus 5.3.4.
   Surface running both
2. Linux Mint chromium browser Floccus 5.4.0 and
3. windows 11 running chrome browser Floccus 5.4.0.

This is my first time using Floccus and i didn't manage to get it to work.

I have WEBDAV server up and running on my Synology NAS, and i verified that it is working alright with various applications.

I suspect the problem is that Floccus doesn't allow self-signed certificates (No option to allow that), because the applications that didn't work are the ones that doesn't allow the self-signed certificates.

my WebDAV URL is https://<tailscale-ip-address>:<port>/Bookmarks File format: XBEL

Note: I use tailscale to access my NAS.

I am having the same error E017 even when using Nextcloud via Chrome or Chromium browsers, but it works fine with Firefox!

[marcelklehr]

So, self-signed certificates are up to the browser. If the browser accepts them, floccus is able to connect, othewise floccus can't do its thing.

[qlifee]

I managed to make it work on all Chromium based browsers, and figured out why it worked fine in Firefox.

In Firefox when first you try to access the server https://<tailscale-ip-address>:<port>/ you'll be prompted to accept the insecure certificate, and once you do that, Firefox will add it in the server certificate error exception under Settings > Privacy & Security > Certificate Manager > Server

This will ensure the connection will be accepted as an exception.

However in Chromium based browsers this doesn't happen. Instead you'll have to:

1- Create a self-signed certificate and a private key (two files) like so:

bash

openssl req -x509 -nodes -days 365 -newkey rsa:2048 \
-keyout server.key -out server.crt \
-subj "/CN=your-ip-address" \
-addext "subjectAltName=IP:your-ip-address"

2- Then combine the generated certificate and the key into one Base-64 Encoded (PEM Format) certificate:

bash

cat server.crt server.key > server.pem

3- Go to Settings > Privacy and Security > Security > Manage certificates > Authorities and Import the .pem certificate.

4- Go to the added certificate starting with org- and click the down arrow, then the three dot icon, then click Edit, and check Trust this certificate for identifying websites.

Now the WebDAV setup with tailscale ip address via floccus will sync, and you won't get the E017 error.

Note: In tailscale settings website make sure to Disable key expiry, this will ensure that this ip address won't be changed automatically.

[qlifee]

I also managed to get it to work on Android, I just installed the .pem certificate under CA Certificates (Settings > Security & privacy > More security & privacy > Encryption & credentials > Install a certificate) and now it works :)

[marcelklehr]

I also managed to get it to work on Android

Oh, then you're the first, I think. Care to share that to the folks at #1560 ?

[snIP3r23]

I have the same isse on Win11 with Firefox 133.0.3 with Floccus 5.4.0. But Im using Lets Encrypt Certificates instead of Self Signed. It seems to work with Android an chrome based Kiwi Browser.

[marcelklehr]

@snIP3r23 Can you create a new issue in this case, as this one is about self-signed certificates?

[marcelklehr]

@hochl Were you able to get it working now?

[hochl]

@hochl Were you able to get it working now?

Hey there! Sorry I am/was busy and will hopefully have time to check it in the new year.

[grg5811]

Good morning everyone,
I followed the method form @qlifee but with more detailed instructions found at https://stackoverflow.com/a/60516812 and, now, everything works perfectly.
I work with Browser brave in Debian 12.
Thank you