E017: Network error: Check your network connection and your account details Last synchronized

[iamhaval]

Which version of floccus are you using?

5.0.10

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.

Floorp 11.11.2, Vivaldi 6.6.3271.55, Android 14

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)

Using WebDAV Server on Synology NAS

Describe the Bug

Shortly after successfully setting up floccus, I receive this error whenever I open the extension. I try to manually sync and it continues to show the same error message. Sometimes it will suddenly sync and the error goes away but for the most part the error is persisting.

E017: Network error: Check your network connection and your account details Last synchronized

Expected Behavior

I expect floccus to sync, whether it's the automatic sync or manual sync.

To Reproduce

All I am doing is launching the browser and checking the floccus extension on both floorp and vivaldi. The same occurs when checking the android app.

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 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]

Hi

Are you using a self-signed certificate for your webdav server?

[marcelklehr]

You are using a self-signed letsencrypt certificate? That sounds like an oxymoron to me 🤔

Did you get the certificate from letsencrypt? Or did you generate it yourself without enlisting a commonly known Certificate Authority?

[iamhaval]

You are using a self-signed letsencrypt certificate? That sounds like an oxymoron to me 🤔

Did you get the certificate from letsencrypt? Or did you generate it yourself without enlisting a commonly known Certificate Authority?

I generated the SSL using the letsencrypt feature built into Nginx Proxy manager is what I meant to say 😉

[iamhaval]

Did you update the browser extensions recently? Suddenly the browser extensions work but only the Android app keeps returning the same error.

[marcelklehr]

Yes, there's a new release out for a few days now

[iamhaval]

Yes, there's a new release out for a few days now

Perfect. And the android app?

[marcelklehr]

Is currently out on F-Droid and in open testing phase on google play and will soon be on production in google play as well

[iamhaval]

I ended up deleting the Android app because even with the new update, it was not syncing.

Now, the browser add-ons are having the same issues again. It was working better there for a day or two, and suddenly it's the same error frequently.

I use let's encrypt SSL on Nginx Proxy. Why is this happening? Why does it work some of the times but not all of the time?

[Eschguy]

just started getting this error on Firefox.

[marcelklehr]

Very strange

[marcelklehr]

Can you rule out Adblockers , other addons or any kind of proxy?

[iamhaval]

Yes, I can rule those out.

[marcelklehr]

Can you check the extension permissions for floccus in chrome://extensions to see whether it can access the network?

[marcelklehr]

It really seems like it's a network thing, but I assume you have ruled that out already, otherwise you wouldn't be here. Maybe it's a browser bug? Can you try with firefox, perhaps?

[iamhaval]

This happening on two separate computers, which both have Floccus installed on Vivaldi and Floorp browsers.

Both browsers allow the extension to very randomly work. Other times it gives that error. So it does work kind of but 50% of the time only. The other 50% it gives that error I mentioned.

As I stated, floccus is hosted on my Synology NAS using WebDav and I use it via HTTPS with an SSL cert from LetsEncrypt.

Also, I have my network on Tailscale, but I don't see why that would be an issue because I self-host a ton of other services and never have had an issue because I understand how it works.

Have you checked the logs I provided?

floccus-5.1.2-2024-05-20-redacted.log

[los0220]

I've had the same error for over a month with self-signed cert and NextCloud bookmarks. When I click DEBUG LOGS, they are empty.
I tried reinstalling the extension and reconnecting without any luck.

[marcelklehr]

@los0220 Chrome does not allow self-signed certificates anymore in extensions it seems. So, I recommend using a let's encrypt cert. (see #1560 )

[marcelklehr]

Have you checked the logs I provided?

The logs don't help, I'm afraid. All floccus sees is the network error that the browser throws.

[marcelklehr]

@iamhaval Perhaps you can dig into the network debug inspector a bit in your browser?

Firefox

• Go to about:debugging
• go to "This firefox"
• click on Inspect button next to floccus entry
• go to the network tab in the inspector
• trigger a sync by clicking on sync now for the account of your choice.
• check the failing network requests

Chrome

• Go to chrome://extensions
• enable Developer mode
• click on Service Worker button in floccus' entry next to "Inspect views: "
• go to the network tab in the inspector window
• trigger a sync by clicking on sync now for the account of your choice
• check the failing network requests

[iamhaval]

@marcelklehr I have run plenty of troubleshooting and I have some consistent results.

When I connect to the WebDav on my NAS using HTTP without any reverse proxy (Nginx), it works flawlessly. The second I use either or both HTTPS and Nginx reverse proxy, this is where the inconsistency issues begin.

Not sure why this is the case, but I was able to narrow it down to this with absolute certainty. Is this something that can be resolved? Why does it have such a hard time when HTTPS, SSL, and Reverse Proxy is involved? It seems to want to only behave on an insecure connection.

[marcelklehr]

I don't know the answer to these questions. If you debug the network requests in the browser debugger you may find the cause for the failed network requests from the perspective of the browser.