Desktop client forever "waiting to start syncing"

My desktop client is stuck forever “waiting to start syncing”, what might be the problem?

My server was a 19.0.1 and is now a 19.0.2 docker container, my database is a Postgres docker container (built from the official images).

When I quit the client and restart it, the Nextcloud log does not contain any new entries, but the client keeps “preparing for sync”. When I modify a file locally, the state switches to “waiting to start syncing” again.

My client runs on KDE neon.

www-data@f914adedc341:~/html$ ./occ status
- installed: true
- version:
- versionstring: 19.0.2
- edition:
$ nextcloud -v
Nextcloud version 3.0.1-20200828.171413.0a62628f8-1.0~focal1
Using Qt 5.14.2, built against Qt 5.12.8
Using Qt platform plugin 'xcb'
Using 'OpenSSL 1.1.1f  31 Mar 2020'
Running on KDE neon User Edition 5.19, x86_64
Operating System: KDE neon 5.19
KDE Plasma Version: 5.19.4
KDE Frameworks Version: 5.73.0
Qt Version: 5.14.2
Kernel Version: 5.7.0-050700-generic
OS Type: 64-bit
Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz
Memory: 23,4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620

Have the same Problem here wit Client 3.0.1 on Linux Mint 20 Cinnamon

1 Like
1 Like

I skimmed through the issue on github.

Do I understand it correctly that so far there is no solution? Or did I miss something?

A (the) workaround is to disable the end-to-end encryption (E2EE) app in the Nextcloud Server instance.

A fix has been merged and released with desktop client version 3.0.3:

But from the ongoing discussion of this pull request I take it that the issue has not been definitively resolved.

Anyways, if you don’t absolutely need E2EE, just disable the app and you’re fine.


not for me, I have 3.0.3 on macOS and had to disable E2EE on the server running NC19.0.4 Stable

How did this issue not already be patched before getting into Stable?

I do not use E2EE and I updated client to 3.0.3 Windows 10 OS. Server is 20.0.2 and my clients on all PCs are stuck in waiting to sync. Issue still not resolved.

1 Like

In my case, deactivating E2EE did help. Windows 10, NCDesktop 3.0.3, Server 20.0.2.
Are we looking at one single issue or are there two issues with the same symptoms (involving/not involving E2EE)?
Anything I can do to help pinpointing?

1 Like

Made sort of same experience with W10 sync client V3.0 months ago. Changing something within sync folders -e.g. adding a file or updating a current one- did the magic in my case…