Skip to content

always network error #1960

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

Open
1 task
pisice opened this issue May 18, 2025 · 2 comments
Open
1 task

always network error #1960

pisice opened this issue May 18, 2025 · 2 comments
Labels

Comments

@pisice
Copy link

pisice commented May 18, 2025

Which version of floccus are you using?

5.5.3.1

How many bookmarks do you have, roughly?

418

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.

android kiwi brower 137.0.73337

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 the webdav server I built myself
by win 10, iis.

Describe the Bug

The new configuration is available, but it won't work after a while.Always prompt for network error. The same server win side is running fine.

Expected Behavior

Normal operation

To Reproduce

android 13
miui 14.0.2

log:
2025-05-18T23:12:53.479Z Starting sync process for account xxxxx
2025-05-18T23:12:53.493Z onSyncStart: begin
2025-05-18T23:12:53.495Z https://xxxx.xxxx.com
2025-05-18T23:12:53.700Z Error Caught
2025-05-18T23:12:53.700Z [TypeError: Failed to fetch]
2025-05-18T23:12:53.702Z Syncing failed with E017: Network error: Check your network connection and your account details
2025-05-18T23:12:53.707Z onSyncFail

Image
Image
Image
Image
Image
Image

Debug log provided

  • I have provided a debug log file
@pisice pisice added the bug label May 18, 2025
Copy link

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 💙

@IssacEinstein
Copy link

2025-05-20T05:47:34.886Z Starting sync process for account @gitea.com:bookmarks.xbel
2025-05-20T05:47:34.898Z onSyncStart: begin
2025-05-20T05:47:34.901Z (git) init
2025-05-20T05:47:36.151Z (git) fetch from remote
2025-05-20T05:47:38.077Z Syncing failed with HTTP Error: 503 Service Unavailable
2025-05-20T05:47:38.079Z onSyncFail

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants