Nextcloud Desktop Client (macOS) freezes during sync – other accounts work fine

ℹ️ Support
, , , , ,
1

Hello,

I’m running the following setup:

  • Hetzner Cloud Server, Ubuntu 20.04.6 LTS
  • Hetzner Storage Box used as the data location (fuse.sshfs)
  • Nextcloud AIO v11.0.0 (Nextcloud 31.0.5)
  • MacBook Pro M1 14″ (2021) running macOS 15.5
  • Nextcloud Desktop Client (macOS) version 3.16.5

Recently, my desktop client has started freezing while syncing. Right after launching the client, it briefly shows:

Bildschirmfoto 2025-06-19 um 21.15.53
Bildschirmfoto 2025-06-19 um 21.15.53824×126 16.9 KB

A moment later, it shows:

Bildschirmfoto 2025-06-19 um 21.16.37

…and then stays stuck in this state.

I can still access the Nextcloud instance via the web interface and the iOS client without any issues. If I log into the Mac under a different user account — one that connects to the same Nextcloud instance but uses a different Nextcloud account — synchronization works without any problems. Additionally, I’ve already signed out of the desktop client and signed back in, but that didn’t change anything.

Upgrading to Nextcloud Desktop Client (macos) 3.16.6 didn’t help, nor did updating to Nextcloud AIO v11.1.0 (Nextcloud 31.0.6).

In the administration settings I see this error:

Der Nextcloud-Server konnte keine Verbindung zum Whiteboard-Server herstellen: Client error: `GET https://nextcloud.familiemarkwirth.de/whiteboard` resulted in a `404 Not Found` response: <!DOCTYPE html> <html class="ng-csp" data-placeholder-focus="false" lang="en" data-locale="en" translate="no" > <head (truncated…)

I don’t recall ever creating or trying to sync a whiteboard document.

The issue first appeared—at least to the best of my recollection—after the update to Nextcloud 31.0.5.

Many thanks for your help,
Lutz

1 Like
2

Do you have a huge amount of data in your account?

There was a message to all forum users:

:warning: Desktop files client 3.16.5 known issue: slow remote discovery on the first run

:bug: In the previous versions the permissions reported by the server were not correctly taken into account. It would fail to detect read only files and it would try to download files without the download permission.

:white_check_mark: 3.16.5 includes a fix for the handling of files permissions. The consequence of it is that the client will need to execute a full remote discovery during the first run to check for the correct permissions and update the files status accordingly. The discovery time might be slow depending on your server settings, on the number of folders and files and on the speed of the network between the client and the server.

:information_source: The recommendation is still to upgrade to 3.16.5 because there are other bug fixes included in this version that might benefit you. In the meantime, we are working on improving the user experience on the first run.

Not sure if this helps you.

1 Like
3

Dear rakekniven,

Thank you very much for your quick response!

Yes, I do indeed have a lot of data in the cloud and also saw the message. To be honest, I wasn’t fully aware of the implications. Does this mean I should ideally keep the client open until all the data has been assigned the new permissions? And how can I tell whether it’s actually working?

Warm regards,
Lutz

4

I would like to emphasize my question again. Does no one else have any ideas? I have not been able to synchronize for weeks now, waiting for an update. But it’s not coming.