Sync issue nextcloud client

[fettfoen]

Server: Nextcloud 21.0.2 Ubuntu 18.04 PHP 7.4 MariaDB 10.5.10 Redis Server 4.0.9

Desktop: Nextcloud Client 3.2.1 (Linux,Mac,Windows)

I configured notifiy_push, followed these instrucions https://github.com/nextcloud/notify_push/blob/main/README.md.

All checks by nextcloud passed!

# sudo -u www-data php /var/www/nextcloud/occ notify_push:setup Push binary seems to be running already ✓ push server seems to be functioning correctly. Reverse proxy seems to be configured already ✓ reverse proxy seems to be setup correctly. configuration saved

SystemD

[Unit] Description = Push daemon for Nextcloud clients [Service] Environment=PORT=7867 Environment=BIND=127.0.0.1 Environment=METRICS_PORT=7868 Environment=NEXTCLOUD_URL=https://cloudtest.mydomain.com ExecStart=/var/www/nextcloud/apps/notify_push/bin/x86_64/notify_push /var/www/nextcloud/config/config.php User=www-data [Install] WantedBy = multi-user.target

Apache2 Reverse Proxy

#push ProxyPass /push/ws ws://127.0.0.1:7867/ws ProxyPass /push/ http://127.0.0.1:7867/ ProxyPassReverse /push/ http://127.0.0.1:7867/

#metrics ProxyPass /metrics http://127.0.0.1:7868/metrics ProxyPassReverse /metrics http://127.0.0.1:7868/

The Problem:

Syncing works pretty well and super fast. I doesnt matter if i create/change/delete folder or files. All changes are applied immediately.

But syncing suddenly stops for no apparent reason. Sometimes it helps to restart the syncing client and sometimes it wont work anymore.

For Example:

I deleted folder "test6" via webui and now syncing stucks. No activity in local client. Just showing the blue syncing icon. Restart doesn't help. I have to delete manually the local folder "test6" and restart the client. Then the synchronization works again for a while. The problem occurs bidirectionally (doesnt matter if i delete/change/create in webui or local).

It is hard to read the logs, but i cant find any information server side. Im trying to add the local client log later, its not possible at this time.

[solracsf]

Can you try switching to Unix socket instead of http

[Service]
Environment=SOCKET_PATH=/var/run/notify_push.sock
...

and see https://serverfault.com/questions/767071/proxypass-a-websocket-connection-to-a-unix-socket

and/or also increase Proxy Timeouts

ProxyPass <connection_here> connectiontimeout=3600 timeout=3600

[solracsf]

See also if you're affected by https://github.com/nextcloud/notify_push/issues/96

[fettfoen]

Can you try switching to Unix socket instead of http

[Service]
Environment=SOCKET_PATH=/var/run/notify_push.sock
...

and see https://serverfault.com/questions/767071/proxypass-a-websocket-connection-to-a-unix-socket

and/or also increase Proxy Timeouts

ProxyPass <connection_here> connectiontimeout=3600 timeout=3600

I will try a soon as possible and give response.

[fettfoen]

Sorry, but i cant get it work with unix socket. Could someone please share their configuration for apache2.

[nursoda]

Does it stop syncing with ALL clients or just some? In my case, it was a sync CLIENT issue that is triggered by two events (separate issues): (1) standby and resume of the client (2) rebooting the server. In both cases, the open push channel was broken resulting in the client not syncing at all since i thought "if there is anything new, I'll be informed". So it stayed put. These issues have been solved by adding a client-side alive-ping. Fixes are merged but will only be released in the 3.3 client series.

I don't have a setup howto for Apache, but maybe my HPB + socket setup guide for NGINX still points you in the right directíon.

[hj-beckers]

Would you mind sharing your setup howto for Apache? Thanks.

[nursoda]

Sorry, that was a "typo" (now corrected). I use NGINX only, so I can't provide a howto for apache2.

[castillo92]

I am having the same issue. When open the WebUI and drop a textfile, it syncs inmediately in the Windows NextCLoud Client, but only once.... The following changes are applied 30 second later or more, like without notify_push

[nursoda]

In case that's what hit you (not very probable since that was after standby/resume): There was an issue with the Sync CLIENT (on Linux). Please make sure you are using the latest sync client (3.3.6 by the time of writing) when doing your test.

[joshtrichards]

Is this still occurring for anyone on this thread? Or have client enhancements made this more robust? I'll close this out if no further followup is received since this issue hasn't seen any traffic for ~2 years.

[nursoda]

Not happening for me with current server and desktop sync client releases.