[GH-ISSUE #1570] E017: Network error: Check your network connection and your account details Last synchronized

kerem commented

2026-02-25 22:38:48 +03:00

Owner

Originally created by @BashBandito on GitHub (Mar 27, 2024).
Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1570

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

Originally created by @BashBandito on GitHub (Mar 27, 2024). Original GitHub issue: https://github.com/floccusaddon/floccus/issues/1570 ### 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 - [X] I have provided a debug log file

kerem

2026-02-25 22:38:48 +03:00

closed this issue
added the
bug

waiting for more information
labels

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Mar 27, 2024):

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 💙

@github-actions[bot] commented on GitHub (Mar 27, 2024): Hello :wave: 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 :blue_heart:

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 21, 2024):

Hi

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

@marcelklehr commented on GitHub (Apr 21, 2024): Hi Are you using a self-signed certificate for your webdav server?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Apr 21, 2024):

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?

@marcelklehr commented on GitHub (Apr 21, 2024): You are using a self-signed letsencrypt certificate? That sounds like an oxymoron to me :thinking: Did you get the certificate from letsencrypt? Or did you generate it yourself without enlisting a commonly known Certificate Authority?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Apr 21, 2024):

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 😉

@BashBandito commented on GitHub (Apr 21, 2024): > You are using a self-signed letsencrypt certificate? That sounds like an oxymoron to me :thinking: > > 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 😉

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 1, 2024):

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

@BashBandito commented on GitHub (May 1, 2024): Did you update the browser extensions recently? Suddenly the browser extensions work but only the Android app keeps returning the same error.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 1, 2024):

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

@marcelklehr commented on GitHub (May 1, 2024): Yes, there's a new release out for a few days now

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 1, 2024):

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

Perfect. And the android app?

@BashBandito commented on GitHub (May 1, 2024): > Yes, there's a new release out for a few days now Perfect. And the android app?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 1, 2024):

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

@marcelklehr commented on GitHub (May 1, 2024): 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

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 5, 2024):

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?

@BashBandito commented on GitHub (May 5, 2024): 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?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@Eschguy commented on GitHub (May 8, 2024):

just started getting this error on Firefox.

@Eschguy commented on GitHub (May 8, 2024): just started getting this error on Firefox.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 9, 2024):

Very strange

@marcelklehr commented on GitHub (May 9, 2024): Very strange

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 10, 2024):

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

@marcelklehr commented on GitHub (May 10, 2024): Can you rule out Adblockers , other addons or any kind of proxy?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 10, 2024):

Yes, I can rule those out.

@BashBandito commented on GitHub (May 10, 2024): Yes, I can rule those out.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 11, 2024):

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

@marcelklehr commented on GitHub (May 11, 2024): Can you check the extension permissions for floccus in chrome://extensions to see whether it can access the network?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 15, 2024):

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?

@marcelklehr commented on GitHub (May 15, 2024): 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?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 20, 2024):

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

@BashBandito commented on GitHub (May 20, 2024): 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](https://github.com/floccusaddon/floccus/files/15381162/floccus-5.1.2-2024-05-20-redacted.log)

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@los0220 commented on GitHub (May 21, 2024):

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.

@los0220 commented on GitHub (May 21, 2024): 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.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 21, 2024):

@los0220 Chrome does not allow self-signed certificates anymore in extensions it seems. So, I recommend using a let's encrypt cert. (see https://github.com/floccusaddon/floccus/issues/1560 )

@marcelklehr commented on GitHub (May 21, 2024): @los0220 Chrome does not allow self-signed certificates anymore in extensions it seems. So, I recommend using a let's encrypt cert. (see https://github.com/floccusaddon/floccus/issues/1560 )

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 21, 2024):

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 commented on GitHub (May 21, 2024): > 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.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 21, 2024):

@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

@marcelklehr commented on GitHub (May 21, 2024): @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

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (May 23, 2024):

@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.

@BashBandito commented on GitHub (May 23, 2024): @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.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (May 24, 2024):

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.

@marcelklehr commented on GitHub (May 24, 2024): 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.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Jun 16, 2024):

This is the HTTP connection that works ☝️

This is the standard HTTPS connection that doesn't work ☝️

This is the Nginx Proxy connection with Lets Encrypt SSL via FQDN that doesn't work ☝️

@BashBandito commented on GitHub (Jun 16, 2024): ![floccus_works_http](https://github.com/floccusaddon/floccus/assets/132589108/464ebe18-252d-4ca9-80ef-ad1bbb4c7d10) This is the HTTP connection that works ☝️ ![floccus_https_doesnt_work](https://github.com/floccusaddon/floccus/assets/132589108/968a9640-019a-459a-ba5c-1174f639f6f8) This is the standard HTTPS connection that doesn't work ☝️ ![Screenshot_20240616_061017](https://github.com/floccusaddon/floccus/assets/132589108/1110b080-0c04-490e-bd8e-79e77cb8f31a) This is the Nginx Proxy connection with Lets Encrypt SSL via FQDN that doesn't work ☝️

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jun 22, 2024):

Is there some kind of exaplanation somewhere in the inspector interface why the requests fail when using HTTPS?

@marcelklehr commented on GitHub (Jun 22, 2024): Is there some kind of exaplanation somewhere in the inspector interface why the requests fail when using HTTPS?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jun 22, 2024):

I think it's likely related to your SSL config. Can you try checking the config using openssl s_client -connect example.com:443 if you're on Linux.

@marcelklehr commented on GitHub (Jun 22, 2024): I think it's likely related to your SSL config. Can you try checking the config using `openssl s_client -connect example.com:443` if you're on Linux.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 21, 2024):

@iamstonecutter ping

@marcelklehr commented on GitHub (Jul 21, 2024): @iamstonecutter ping

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Jul 21, 2024):

I think it's likely related to your SSL config. Can you try checking the config using openssl s_client -connect example.com:443 if you're on Linux.

Sorry for the late response.

Is it safe to paste the terminal output of that command in here?

@BashBandito commented on GitHub (Jul 21, 2024): > I think it's likely related to your SSL config. Can you try checking the config using `openssl s_client -connect example.com:443` if you're on Linux. Sorry for the late response. Is it safe to paste the terminal output of that command in here?

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 21, 2024):

Is it safe to paste the terminal output of that command in here?

I believe so. You might want to change the actual domain / IP addresses

@marcelklehr commented on GitHub (Jul 21, 2024): > Is it safe to paste the terminal output of that command in here? I believe so. You might want to change the actual domain / IP addresses

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Jul 21, 2024):

Is it safe to paste the terminal output of that command in here?

I believe so

I think it's likely related to your SSL config. Can you try checking the config using openssl s_client -connect example.com:443 if you're on Linux.

I hope this is what you were asking to see.

I'll re-generate a new SSL after anyway, just to be safe.

MyNAS:~$ openssl s_client -connect mydomain.com:443
CONNECTED(00000003)
depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1
verify return:1
depth=1 C = US, O = Let's Encrypt, CN = E6
verify return:1
depth=0 CN = *.mydomain.com
verify return:1
---
Certificate chain
 0 s:CN = *.mydomain.com
   i:C = US, O = Let's Encrypt, CN = E6
 1 s:C = US, O = Let's Encrypt, CN = E6
   i:C = US, O = Internet Security Research Group, CN = ISRG Root X1
---
Server certificate
-----BEGIN CERTIFICATE-----
**REDACTED**
-----END CERTIFICATE-----
subject=CN = *.mydomain.com

issuer=C = US, O = Let's Encrypt, CN = E6

---
No client certificate CA names sent
Peer signing digest: SHA384
Peer signature type: ECDSA
Server Temp Key: X25519, 253 bits
---
SSL handshake has read 2464 bytes and written 394 bytes
Verification: OK
---
New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384
Server public key is 384 bit
Secure Renegotiation IS NOT supported
No ALPN negotiated
Early data was not sent
Verify return code: 0 (ok)
---
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: CAD6D7054BA59ECEFFE96AD260332C3C33893FC0E3CF23C28EC775E0F2F8CBD7
    Session-ID-ctx: 
    Resumption PSK: 0E3FE5A5AC962C30371C85767428D216F9683C3FCAB75A016E77DC2378E21078A067D58221A508240472F81250E32294
    PSK identity: None
    PSK identity hint: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 48 c0 8a 48 59 31 2e 86-d4 f0 82 d1 43 95 3d ca   H..HY1......C.=.
    0010 - b4 71 fe f3 25 2b 46 f4-0b 8b 21 2e c0 76 4e 29   .q..%+F...!..vN)
    0020 - b9 16 ca 6b 22 3d 6e 45-0f c4 e9 a7 7a bc f6 65   ...k"=nE....z..e
    0030 - 67 8a 96 44 14 7a 09 89-46 dc 71 e0 77 b5 53 11   g..D.z..F.q.w.S.
    0040 - ab 56 ad 6e c6 39 dd 2d-d7 f8 88 87 98 83 67 dc   .V.n.9.-......g.
    0050 - 6b c4 1a ec ec a6 e8 15-04 84 7c 56 df 80 72 38   k.........|V..r8
    0060 - d9 5c 5e 91 a7 56 9b e5-a6 e0 30 3e 68 3b 80 41   .\^..V....0>h;.A
    0070 - 64 2e 3e 4b fe f9 29 b0-2b 56 a7 1a 3d 37 7a 06   d.>K..).+V..=7z.
    0080 - 27 ba 49 e6 78 bb 73 dc-2e 35 b8 56 9b 27 3c 79   '.I.x.s..5.V.'<y
    0090 - cf 3f d0 6e be 43 f4 7e-66 8b b4 c9 dc c7 82 3c   .?.n.C.~f......<
    00a0 - fe b9 c0 a7 26 f7 9c 7c-3a ac fe fc 4f ad 5a f4   ....&..|:...O.Z.
    00b0 - 45 f2 be d1 71 39 bc 6a-6a 0c c2 fb d4 05 6b ae   E...q9.jj.....k.
    00c0 - 39 b9 fc 10 85 4c c8 2e-10 5c 2d 6d ec 1b 51 6e   9....L...\-m..Qn
    00d0 - b0 50 47 cc 46 39 99 7a-d5 90 5a 51 56 c2 73 89   .PG.F9.z..ZQV.s.
    00e0 - 5e e7 bc bd 4e b9 a1 e9-bc 9e 6c 05 29 1e 62 71   ^...N.....l.).bq

    Start Time: 1721576387
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
---
Post-Handshake New Session Ticket arrived:
SSL-Session:
    Protocol  : TLSv1.3
    Cipher    : TLS_AES_256_GCM_SHA384
    Session-ID: AAB2D3FEBB7743294656D7A3F69F7D05192FEB833FE2BEB4062C48AF47B58441
    Session-ID-ctx: 
    Resumption PSK: 549B22FDB5F43BB5B081B064900A27EA9942252863F215B109F81E18FA2995BB65BFDBF6BEAE45BC619793683D9C52AD
    PSK identity: None
    PSK identity hint: None
    TLS session ticket lifetime hint: 300 (seconds)
    TLS session ticket:
    0000 - 48 c0 8a 48 59 31 2e 86-d4 f0 82 d1 43 95 3d ca   H..HY1......C.=.
    0010 - b7 68 7f cd 7b 80 5c d0-22 83 91 78 81 b8 bf 39   .h..{.\."..x...9
    0020 - cf 19 b8 3a 46 e7 61 58-d5 c7 56 f9 54 fb d5 d7   ...:F.aX..V.T...
    0030 - ac 08 2b 1c 89 74 6b 5e-0d 6e f2 de 85 6e 2a 1f   ..+..tk^.n...n*.
    0040 - bb 9d 02 e9 d8 19 ff 84-f6 44 5d 77 62 b8 f9 f3   .........D]wb...
    0050 - 4f 81 46 79 8f 6f 7c 46-e0 5f 68 79 07 33 01 dd   O.Fy.o|F._hy.3..
    0060 - a1 5d c0 64 78 7b 16 cf-eb 19 dd 29 c1 d9 c8 dc   .].dx{.....)....
    0070 - cc 96 d4 16 9e 58 34 16-fb 09 db 3b 1d a2 a1 02   .....X4....;....
    0080 - 25 74 b0 2d 74 b6 55 cb-87 ca 2c e0 3c 34 03 66   %t.-t.U...,.<4.f
    0090 - e7 7a 46 3d 23 39 b3 df-5e 67 8b d3 96 11 68 0e   .zF=#9..^g....h.
    00a0 - 60 d8 fb da c3 d4 40 7b-be bd a2 73 69 cf 6e 2d   `.....@{...si.n-
    00b0 - f9 73 43 29 62 50 bc 09-28 26 c1 26 33 0e 38 bf   .sC)bP..(&.&3.8.
    00c0 - 6d c2 b3 52 de 9c 11 fa-7a 07 09 d6 2a 54 79 a0   m..R....z...*Ty.
    00d0 - 72 eb b7 9c fc 43 7d 19-3d 3e 29 85 f3 66 3c 29   r....C}.=>)..f<)
    00e0 - c7 2c cf 26 a6 79 62 cc-24 eb cd 41 05 cd 7c 4c   .,.&.yb.$..A..|L

    Start Time: 1721576387
    Timeout   : 7200 (sec)
    Verify return code: 0 (ok)
    Extended master secret: no
    Max Early Data: 0
---
read R BLOCK
closed

@BashBandito commented on GitHub (Jul 21, 2024): > > Is it safe to paste the terminal output of that command in here? > > I believe so > I think it's likely related to your SSL config. Can you try checking the config using `openssl s_client -connect example.com:443` if you're on Linux. I hope this is what you were asking to see. I'll re-generate a new SSL after anyway, just to be safe. ``` MyNAS:~$ openssl s_client -connect mydomain.com:443 CONNECTED(00000003) depth=2 C = US, O = Internet Security Research Group, CN = ISRG Root X1 verify return:1 depth=1 C = US, O = Let's Encrypt, CN = E6 verify return:1 depth=0 CN = *.mydomain.com verify return:1 --- Certificate chain 0 s:CN = *.mydomain.com i:C = US, O = Let's Encrypt, CN = E6 1 s:C = US, O = Let's Encrypt, CN = E6 i:C = US, O = Internet Security Research Group, CN = ISRG Root X1 --- Server certificate -----BEGIN CERTIFICATE----- **REDACTED** -----END CERTIFICATE----- subject=CN = *.mydomain.com issuer=C = US, O = Let's Encrypt, CN = E6 --- No client certificate CA names sent Peer signing digest: SHA384 Peer signature type: ECDSA Server Temp Key: X25519, 253 bits --- SSL handshake has read 2464 bytes and written 394 bytes Verification: OK --- New, TLSv1.3, Cipher is TLS_AES_256_GCM_SHA384 Server public key is 384 bit Secure Renegotiation IS NOT supported No ALPN negotiated Early data was not sent Verify return code: 0 (ok) --- --- Post-Handshake New Session Ticket arrived: SSL-Session: Protocol : TLSv1.3 Cipher : TLS_AES_256_GCM_SHA384 Session-ID: CAD6D7054BA59ECEFFE96AD260332C3C33893FC0E3CF23C28EC775E0F2F8CBD7 Session-ID-ctx: Resumption PSK: 0E3FE5A5AC962C30371C85767428D216F9683C3FCAB75A016E77DC2378E21078A067D58221A508240472F81250E32294 PSK identity: None PSK identity hint: None TLS session ticket lifetime hint: 300 (seconds) TLS session ticket: 0000 - 48 c0 8a 48 59 31 2e 86-d4 f0 82 d1 43 95 3d ca H..HY1......C.=. 0010 - b4 71 fe f3 25 2b 46 f4-0b 8b 21 2e c0 76 4e 29 .q..%+F...!..vN) 0020 - b9 16 ca 6b 22 3d 6e 45-0f c4 e9 a7 7a bc f6 65 ...k"=nE....z..e 0030 - 67 8a 96 44 14 7a 09 89-46 dc 71 e0 77 b5 53 11 g..D.z..F.q.w.S. 0040 - ab 56 ad 6e c6 39 dd 2d-d7 f8 88 87 98 83 67 dc .V.n.9.-......g. 0050 - 6b c4 1a ec ec a6 e8 15-04 84 7c 56 df 80 72 38 k.........|V..r8 0060 - d9 5c 5e 91 a7 56 9b e5-a6 e0 30 3e 68 3b 80 41 .\^..V....0>h;.A 0070 - 64 2e 3e 4b fe f9 29 b0-2b 56 a7 1a 3d 37 7a 06 d.>K..).+V..=7z. 0080 - 27 ba 49 e6 78 bb 73 dc-2e 35 b8 56 9b 27 3c 79 '.I.x.s..5.V.'<y 0090 - cf 3f d0 6e be 43 f4 7e-66 8b b4 c9 dc c7 82 3c .?.n.C.~f......< 00a0 - fe b9 c0 a7 26 f7 9c 7c-3a ac fe fc 4f ad 5a f4 ....&..|:...O.Z. 00b0 - 45 f2 be d1 71 39 bc 6a-6a 0c c2 fb d4 05 6b ae E...q9.jj.....k. 00c0 - 39 b9 fc 10 85 4c c8 2e-10 5c 2d 6d ec 1b 51 6e 9....L...\-m..Qn 00d0 - b0 50 47 cc 46 39 99 7a-d5 90 5a 51 56 c2 73 89 .PG.F9.z..ZQV.s. 00e0 - 5e e7 bc bd 4e b9 a1 e9-bc 9e 6c 05 29 1e 62 71 ^...N.....l.).bq Start Time: 1721576387 Timeout : 7200 (sec) Verify return code: 0 (ok) Extended master secret: no Max Early Data: 0 --- read R BLOCK --- Post-Handshake New Session Ticket arrived: SSL-Session: Protocol : TLSv1.3 Cipher : TLS_AES_256_GCM_SHA384 Session-ID: AAB2D3FEBB7743294656D7A3F69F7D05192FEB833FE2BEB4062C48AF47B58441 Session-ID-ctx: Resumption PSK: 549B22FDB5F43BB5B081B064900A27EA9942252863F215B109F81E18FA2995BB65BFDBF6BEAE45BC619793683D9C52AD PSK identity: None PSK identity hint: None TLS session ticket lifetime hint: 300 (seconds) TLS session ticket: 0000 - 48 c0 8a 48 59 31 2e 86-d4 f0 82 d1 43 95 3d ca H..HY1......C.=. 0010 - b7 68 7f cd 7b 80 5c d0-22 83 91 78 81 b8 bf 39 .h..{.\."..x...9 0020 - cf 19 b8 3a 46 e7 61 58-d5 c7 56 f9 54 fb d5 d7 ...:F.aX..V.T... 0030 - ac 08 2b 1c 89 74 6b 5e-0d 6e f2 de 85 6e 2a 1f ..+..tk^.n...n*. 0040 - bb 9d 02 e9 d8 19 ff 84-f6 44 5d 77 62 b8 f9 f3 .........D]wb... 0050 - 4f 81 46 79 8f 6f 7c 46-e0 5f 68 79 07 33 01 dd O.Fy.o|F._hy.3.. 0060 - a1 5d c0 64 78 7b 16 cf-eb 19 dd 29 c1 d9 c8 dc .].dx{.....).... 0070 - cc 96 d4 16 9e 58 34 16-fb 09 db 3b 1d a2 a1 02 .....X4....;.... 0080 - 25 74 b0 2d 74 b6 55 cb-87 ca 2c e0 3c 34 03 66 %t.-t.U...,.<4.f 0090 - e7 7a 46 3d 23 39 b3 df-5e 67 8b d3 96 11 68 0e .zF=#9..^g....h. 00a0 - 60 d8 fb da c3 d4 40 7b-be bd a2 73 69 cf 6e 2d `.....@{...si.n- 00b0 - f9 73 43 29 62 50 bc 09-28 26 c1 26 33 0e 38 bf .sC)bP..(&.&3.8. 00c0 - 6d c2 b3 52 de 9c 11 fa-7a 07 09 d6 2a 54 79 a0 m..R....z...*Ty. 00d0 - 72 eb b7 9c fc 43 7d 19-3d 3e 29 85 f3 66 3c 29 r....C}.=>)..f<) 00e0 - c7 2c cf 26 a6 79 62 cc-24 eb cd 41 05 cd 7c 4c .,.&.yb.$..A..|L Start Time: 1721576387 Timeout : 7200 (sec) Verify return code: 0 (ok) Extended master secret: no Max Early Data: 0 --- read R BLOCK closed ```

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 22, 2024):

mh, looks alright, indeed

@marcelklehr commented on GitHub (Jul 22, 2024): mh, looks alright, indeed

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Jul 22, 2024):

Interesting…. Well, I have no clue what's going on.

Floccus is the only self-hosted service on my NAS that has this issue with HTTPS, and I am self-hosting about two dozen services with this same certificate with no issues.

@BashBandito commented on GitHub (Jul 22, 2024): Interesting…. Well, I have no clue what's going on. Floccus is the only self-hosted service on my NAS that has this issue with HTTPS, and I am self-hosting about two dozen services with this same certificate with no issues.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 22, 2024):

In the Network debugger above, can you see a column called "status", this should tell us why the request failed.

@marcelklehr commented on GitHub (Jul 22, 2024): In the Network debugger above, can you see a column called "status", this should tell us why the request failed.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Jul 22, 2024):

You mean this?

Same behaviour as always. Syncs and looks good and then suddenly stops syncing and gives errors. Then 30 to 60 mins later randomly starts syncing again. Rinse and repeat.

It's not a matter of it either works or doesn't. It works and stops and suddenly works again without changing anything. Very strange.

@BashBandito commented on GitHub (Jul 22, 2024): You mean this? ![image](https://github.com/user-attachments/assets/436d93ad-9dd8-499f-9ad5-2090587e7f78) Same behaviour as always. Syncs and looks good and then suddenly stops syncing and gives errors. Then 30 to 60 mins later randomly starts syncing again. Rinse and repeat. It's not a matter of it either works or doesn't. It works and stops and suddenly works again without changing anything. Very strange.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 23, 2024):

Thank you for the screenshot. Since it says ERR_NAME_NOT_RESOLVED, it would seem to be a DNS issue then 🤔

@marcelklehr commented on GitHub (Jul 23, 2024): Thank you for the screenshot. Since it says ERR_NAME_NOT_RESOLVED, it would seem to be a DNS issue then :thinking:

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Jul 23, 2024):

I researched this a bit and it seems that perhaps chrome is running out of sockets:

When this happens, can you try

a dns cache flush which can be done on: chrome://net-internals/#dns
a flush of socket pools which can be done on chrome://net-internals/#sockets

@marcelklehr commented on GitHub (Jul 23, 2024): I researched this a bit and it seems that perhaps chrome is running out of sockets: When this happens, can you try 1. a dns cache flush which can be done on: chrome://net-internals/#dns 2. a flush of socket pools which can be done on chrome://net-internals/#sockets

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Aug 3, 2024):

Just curious, are you thinking that it might be the browser? I ask this because it also happens with Firefox.

Also, I am curious if this would potentially have something to do with my Pi-hole or Tailscale? When you say DNS, the first thing that comes to my mind is my Pi-hole. It is set up on my entire home network, and it's also setup as the DNS server for all my Tailnet devices through the Tailscale config.

Btw, I really do appreciate you continuing to help with trying to find the root cause of this issue.

@BashBandito commented on GitHub (Aug 3, 2024): Just curious, are you thinking that it might be the browser? I ask this because it also happens with Firefox. Also, I am curious if this would potentially have something to do with my Pi-hole or Tailscale? When you say DNS, the first thing that comes to my mind is my Pi-hole. It is set up on my entire home network, and it's also setup as the DNS server for all my Tailnet devices through the Tailscale config. Btw, I really do appreciate you continuing to help with trying to find the root cause of this issue.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 4, 2024):

Just curious, are you thinking that it might be the browser? I ask this because it also happens with Firefox.

Oh. So far I've assumed it only happens with Chrome, because I have the same error in my chrome tests for Nextcloud Bookmarks, but I cannot reproduce this locally.

DNS would indicate it may be a problem with Pi-hole or Tailscale, yes, although I'm also using pi-hole at home without problems.

@marcelklehr commented on GitHub (Aug 4, 2024): > Just curious, are you thinking that it might be the browser? I ask this because it also happens with Firefox. Oh. So far I've assumed it only happens with Chrome, because I have the same error in my chrome tests for Nextcloud Bookmarks, but I cannot reproduce this locally. DNS would indicate it may be a problem with Pi-hole or Tailscale, yes, although I'm also using pi-hole at home without problems.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@BashBandito commented on GitHub (Aug 11, 2024):

It certainly occurs with both Firefox and Chrome.

No clue what it could be, especially considering I have the other two dozen self-hosted apps on my NAS working with HTTPS connections flawlessly. I would imagine if there was something going on with my side of setup that I would see some sort of connection or sync issue in some capacity with the other services I have.

I really am puzzled.

@BashBandito commented on GitHub (Aug 11, 2024): It certainly occurs with both Firefox and Chrome. No clue what it could be, especially considering I have the other two dozen self-hosted apps on my NAS working with HTTPS connections flawlessly. I would imagine if there was something going on with my side of setup that I would see some sort of connection or sync issue in some capacity with the other services I have. I really am puzzled.

kerem commented

2026-02-25 22:38:48 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 12, 2024):

For your other self-hosted apps do you have browser extensions that interface with them as well?

@marcelklehr commented on GitHub (Aug 12, 2024): For your other self-hosted apps do you have browser extensions that interface with them as well?

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@BashBandito commented on GitHub (Aug 12, 2024):

For your other self-hosted apps do you have browser extensions that interface with them as well?

Yes, sir, I do. I self-host vaultwarden on the same NAS as Floccus, and it uses HTTPS.

@BashBandito commented on GitHub (Aug 12, 2024): > For your other self-hosted apps do you have browser extensions that interface with them as well? Yes, sir, I do. I self-host vaultwarden on the same NAS as Floccus, and it uses HTTPS.

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@sunjam commented on GitHub (Aug 20, 2024):

fyi, this is the exact same message displayed by the Floccus app on Android if it is in airplane mode and attempting to sync with the internet disabled.

@sunjam commented on GitHub (Aug 20, 2024): fyi, this is the exact same message displayed by the Floccus app on Android if it is in airplane mode and attempting to sync with the internet disabled.

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@BashBandito commented on GitHub (Aug 20, 2024):

fyi, this is the exact same message displayed by the Floccus app on Android if it is in airplane mode and attempting to sync with the internet disabled.

Hi! Is there something you're thinking that I might not be picking up on?

@BashBandito commented on GitHub (Aug 20, 2024): > fyi, this is the exact same message displayed by the Floccus app on Android if it is in airplane mode and attempting to sync with the internet disabled. Hi! Is there something you're thinking that I might not be picking up on?

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@sunjam commented on GitHub (Aug 20, 2024):

Unsure, so just an fyi.

@sunjam commented on GitHub (Aug 20, 2024): Unsure, so just an fyi.

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@marcelklehr commented on GitHub (Aug 26, 2024):

Mmmh, all very strange, I think the airplane mode is likely not the culprit, thanks for the fyi, though, @sunjam :)

@marcelklehr commented on GitHub (Aug 26, 2024): Mmmh, all very strange, I think the airplane mode is likely not the culprit, thanks for the fyi, though, @sunjam :)

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@BashBandito commented on GitHub (Sep 17, 2024):

I resolved the issue by switching my reverse proxy setup. Previously, I was running Nginx Proxy Manager from within a Docker container on a different subnet than my main network. After moving Nginx Proxy Manager to operate on the same subnet as my primary network, the errors completely disappeared.

While I'm unsure of the exact reason behind this, it's clear that running the reverse proxy on a separate subnet through docker was the cause of the issue.

@BashBandito commented on GitHub (Sep 17, 2024): I resolved the issue by switching my reverse proxy setup. Previously, I was running Nginx Proxy Manager from within a Docker container on a different subnet than my main network. After moving Nginx Proxy Manager to operate on the same subnet as my primary network, the errors completely disappeared. While I'm unsure of the exact reason behind this, it's clear that running the reverse proxy on a separate subnet through docker was the cause of the issue.

kerem commented

2026-02-25 22:38:49 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 18, 2025):

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions[bot] commented on GitHub (Sep 18, 2025): This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

Rows
Columns

[GH-ISSUE #1570] E017: Network error: Check your network connection and your account details Last synchronized #1037

Which version of floccus are you using?

Sync method

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

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

Which version of Nextcloud? (if relevant)

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

Describe the Bug

Expected Behavior

To Reproduce

Debug log provided

Firefox

Chrome