E017: Network error when using Nextcloud through tailscale

[Welved]

Which version of floccus are you using?

Brave (Chrome) 5.4.5

How many bookmarks do you have, roughly?

12k

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

No

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

Which version of Nextcloud Bookmarks are you using? (if relevant)

15.1.0

Which version of Nextcloud? (if relevant)

Linuxserver.io version:- 31.0.2-ls375 Build-date:- 2025-04-01T11:51:43+00:00

What kind of WebDAV server are you using? (if relevant)

No response

Describe the Bug

I've seen other discussions and everyone seems to default to "SSL issue". I personally have both nginx proxy manager and adguardhome setup. When I attempt to sync with floccus, it gives me a

E017: Network error: Check your network connection and your account details | Last synchronized: 0 seconds ago.

Which doesn't make any sense, because floccus isn't even calling out to to anything; looking at my adguardhome. Other than SSL, which I have setup via nginx with cloudflare. Every discussion that I can find, leads no where or gets closed for some reason/excuse.

Expected Behavior

Install the floccus extension to sync my bookmarks to my nextcloud.
Get met with E017: Network error: Check your network connection and your account details | Last synchronized: 0 seconds ago

To Reproduce

Install the floccus extension to sync my bookmarks to my nextcloud.
Get met with E017: Network error: Check your network connection and your account details | Last synchronized: 0 seconds ago

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. Let me give you a short introduction on what to expect from this issue tracker to avoid misunderstandings.
I'm Marcel. I created floccus a few years ago, and have been maintaining it 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. It helps when you stick around to answer follow up questions I may have,
as very few bugs can be fixed directly from the first bug report, without any interaction. If information is missing in your bug report
and the issue cannot be solved without it, I will have to close the issue after a while.
Note also that GitHub in general 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!
If you cannot lend a helping hand, to continue the development and maintenance of this project in a sustainable way,
I ask that you donate to the project when opening an issue (or at least once your issue is solved), 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.

Thank you for reading through this primer. I look forward to working with you on this issue!
Cheers 💙

[marcelklehr]

Hey @Welved
I'm sorry for the trouble and will do my best to help you figure this out.

Can you try checking the network logs of the extension as follows to see if it actually calls out to your server and what happens then:

• Go to brave://extensions
• Enable developer mode
• Click inspect views: service worker
• In the newly opening Inspector window, go to the network tab
• Now, trigger a sync run and check the network tab, ideally you could make a screenshot and send it here. Make sure to redact any sensitive information.

[Welved]

Hey @Welved I'm sorry for the trouble and will do my best to help you figure this out.

Can you try checking the network logs of the extension as follows to see if it actually calls out to your server and what happens then:

• Go to brave://extensions
• Enable developer mode
• Click inspect views: service worker
• In the newly opening Inspector window, go to the network tab
• Now, trigger a sync run and check the network tab, ideally you could make a screenshot and send it here. Make sure to redact any sensitive information.

Fetch⚙ error_32.png
⚙ bookmark?page=1&limit=1
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png

The extension looks to claim, it is unable to communicate with my nextcloud. Visiting my nextcloud via web browser and even using the thing on my phone and PC, I have absolutely no issues.

I have a subdomain setup with NPM, but I don't have it going to my domain provider. I am just simply using my domain, without having it forward onto my provider.

I have my Pi5 route out to tailscale and I use my tailscale assigned IP with my NPM.

When I go and attempt to connect to the floccus app on my phone, I get error:

java.security.cert.CertPathValidatorException: Trust anchor for certification path not found.

Which makes no amount of sense. I have a cert setup with letsencrypt via NPM with the provider being cloudflare.

Unless, I have to make my nextcloud publicly available to have it function? Which I would love to avoid.

[Welved]

Periodically floccus attempts to sync, which it looks like it actually is; but... it quickly fails.

[marcelklehr]

Fetch⚙ error_32.png
⚙ bookmark?page=1&limit=1
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png

I can sadly not deduce much from this :/ Could you do a screenshot with one of the failing requests selected and redact sensitive information?

[Welved]

Fetch⚙ error_32.png
⚙ bookmark?page=1&limit=1
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png
⚙ lock
Fetch⚙ error_32.png
Fetch⚙ error_32.png

I can sadly not deduce much from this :/ Could you do a screenshot with one of the failing requests selected and redact sensitive information?

Here ya go, https://imgur.com/a/8fFRkTK

[marcelklehr]

Mh, I still don't see the reason for the request failure in the screenshot. Could you open the response headers field? Or can you see yourself anywhere a reason for why the requests are red?

[Welved]

Mh, I still don't see the reason for the request failure in the screenshot. Could you open the response headers field? Or can you see yourself anywhere a reason for why the requests are red?

There is nothing in the header response.

[marcelklehr]

Mh. It's strange. As I said, I cannot reproduce with the instructions you provided. Simply setting up a profile and pointing it to a nextcloud works for me, but not for you apparently. For me, this points to a configuration problem. Could you try with a different browser perhaps? To rule that out? Maybe the requests are being adblocked by brave?

[Welved]

Mh. It's strange. As I said, I cannot reproduce with the instructions you provided. Simply setting up a profile and pointing it to a nextcloud works for me, but not for you apparently. For me, this points to a configuration problem. Could you try with a different browser perhaps? To rule that out? Maybe the requests are being adblocked by brave?

Welp. Is floccus unable to sync locally? Does it need to reach out to the internet to grab something?

My nextcloud is behind tailscale and I have it subdomained via NPM, using my tailscale's 100.x.x.x address and it works fine when I access it via the assigned subdomain I gave it. I do own the TLD I am using. Nextcloud itself is a container in docker and the variant that I am using is linuxserver.

What is weird about it is, I had no issues with syncing when I tunneled my Nextcloud via cloudflare? I do have a SSL via letsencrypt with NPM using Cloudflare as it's provider.

[marcelklehr]

Is floccus unable to sync locally?

Using a local IP works for me. From your setup, it may be a DNS issue: It could be that floccus is for some reason using the public DNS information for that domain instead of asking tailscale.

[Welved]

Is floccus unable to sync locally?

Using a local IP works for me. From your setup, it may be a DNS issue: It could be that floccus is for some reason using the public DNS information for that domain instead of asking tailscale.

Well now I am stumped. I have a wild card setup through AdguardHome to point straight to the machine that has nextcloud that is on my tailscale.

Would using a legit TLD locally be a issue? I would imagine it not being a issue? On my domain, all I have is a email aliasing service that I use my own domain for. Would it conflict with that for some reason?

[marcelklehr]

I'm sorry to say I can't really help you much as I don't know much about tailscale / AdguardHome. All I know is, floccus should use the same DNS and network as your browser.

On my domain, all I have is a email aliasing service that I use my own domain for. Would it conflict with that for some reason?

Should not be an issue.

Would using a legit TLD locally be a issue?

You mean you're using something like mydomain.com when you have don't have control over the domain? That could be an issue, but as per above it should be the same issue in your browser then. Or do you mean that you have a domain, but only populate it with records with your own local DNS server (AdGuard Home, I presume).

[Welved]

I'm sorry to say I can't really help you much as I don't know much about tailscale / AdguardHome. All I know is, floccus should use the same DNS and network as your browser.

On my domain, all I have is a email aliasing service that I use my own domain for. Would it conflict with that for some reason?

Should not be an issue.

Would using a legit TLD locally be a issue?

You mean you're using something like mydomain.com when you have don't have control over the domain? That could be an issue, but as per above it should be the same issue in your browser then. Or do you mean that you have a domain, but only populate it with records with your own local DNS server (AdGuard Home, I presume).

Yes my own TLD through cloudflare. No, I don't have any records set for anything besides for the email aliasing. I am merely using my TLD with NPM to assign my local services with a sub domain.

[marcelklehr]

Have you ever successfully accessed those subdomains from anywhere? How do you make sure computers, especially your know about your subdomains?

This is most likely an infrastructure issue unrelated to floccus. I recommend to

1. Check DNS Settings: Verify that the Tailscale client is configured to use the local DNS server where NPM is set up.
2. Review Tailscale Configuration: Ensure that Tailscale is not configured to bypass local DNS queries.
3. Test DNS Resolution: Use tools like nslookup or dig on the Tailscale client to test if it can resolve the domains managed by NPM.

And am closing this issue, because floccus works fine with Nextcloud Bookmarks without tailscale. If it doesn't work with tailscale, then I think it's most likely that tailscale or the tailscale configuration is to blame.

I'm sorry I can't be of more help, I'm not a tailscale expert.