Skip to content
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

[Bug]: Network error occurred: client will retry syncing #5854

Open
5 of 8 tasks
JustRedTTG opened this issue Jul 3, 2023 · 3 comments
Open
5 of 8 tasks

[Bug]: Network error occurred: client will retry syncing #5854

JustRedTTG opened this issue Jul 3, 2023 · 3 comments

Comments

@JustRedTTG
Copy link

⚠️ Before submitting, please verify the following: ⚠️

Bug description

Nextcloud spams this erorr, to the point that I can't check if it even synced anything or not. The profile is synced and virtual downloads work, so not too sure what network error when the network is stable 30MB /s

Steps to reproduce

  1. Click on nextcloud in the bottom right on windows
  2. You will see loads of (X) Network error occurred: client will retry syncing.

Expected behavior

There shouldn't be such error in any condition when the network isn't at fault.

Which files are affected by this bug

idk

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Other

Nextcloud Server version

26.0.0

Nextcloud Desktop Client version

3.9.0

Is this bug present after an update or on a fresh install?

Fresh desktop client install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  • Default internal user-backend
  • LDAP/ Active Directory
  • SSO - SAML
  • Other

Nextcloud Server logs

No response

Additional info

No response

@SeDi343
Copy link

SeDi343 commented Jul 11, 2023

Same Issue. Sync is restarting over and over because of this Error.

@joshtrichards
Copy link
Member

Can you provide the log entries from occur during these events?

@JustRedTTG
Copy link
Author

Can you provide the log entries from occur during these events?

Only happened once or twice, guessing it has certain conditions to occur, if anyone witnesses this bug again they should try to get logs to fix the edge case

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

No branches or pull requests

4 participants