nextcloud / nextcloud/notify_push
The Nextcloud client syncs every few seconds.
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 344
- Forks
- 64
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 5
Description
I hope I’m in the right place here. I’m dealing with an issue involving the Nextcloud client and client push.
The problem is that the Nextcloud client tries to sync every few seconds.
This leads to synchronization conflicts and errors.
If I disable client push, the constant synchronization attempts stop.
The downside is that file changes are then no longer synced promptly from Nextcloud to the client.
I have tried the following:
Disabling files:scan in cron for external file changes. No improvement.
Adjusting the fstab settings, since my data is stored on an SMB share. No improvement.
I documented all of my troubleshooting attempts here.
https://help.nextcloud.com/t/nextcloud-desktop-client-sync-probleme/241833
Unfortunately, the community has not been able to help me either.
Steps to reproduce
- The Nextcloud client syncs every few seconds.
- Disable client push and the constant syncing stops. However, files changed in Nextcloud are then no longer transferred promptly.
- Re-enable client push, and it stops syncing every second. But as soon as a file is changed in Nextcloud, the whole thing starts over again and the sync client wants to update every few seconds.
Expected behaviour
Tell us what should happen
Actual behaviour
Server configuration
Web server: Nginx
Database: Maria
PHP version: 8.4
Nextcloud version: 33.0.2
List of activated apps
If you have access to your command line run e.g.:
sudo -u www-data php occ app:list
from within your Nextcloud installation folder
Enabled: - activity: 6.0.0 - admin_audit: 1.23.0 - agenda_bot: 1.6.1 - announcementcenter: 7.3.0 - app_api: 33.0.0 - assistant: 3.3.0 - bruteforcesettings: 6.0.0 - calendar: 6.2.2 - call_summary_bot: 3.3.0 - circles: 33.0.0 - cloud_federation_api: 1.17.0 - collectives: 4.2.0 - comments: 1.23.0 - contacts: 8.4.4 - contactsinteraction: 1.14.1 - context_chat: 5.3.1 - csp_editor: 1.9.0 - dashboard: 7.13.0 - dav: 1.36.0 - deck: 1.17.1 - external: 8.0.0 - federatedfilesharing: 1.23.0 - federation: 1.23.0 - files: 2.5.0 - files_antivirus: 6.2.0 - files_automatedtagging: 4.0.0 - files_downloadlimit: 5.1.0 - files_fulltextsearch: 33.0.0 - files_pdfviewer: 6.0.0 - files_reminders: 1.6.0 - files_retention: 4.0.1 - files_sharing: 1.25.2 - files_trashbin: 1.23.0 - files_versions: 1.26.0 - forms: 5.2.7 - fulltextsearch: 33.0.0 - fulltextsearch_elasticsearch: 33.0.0 - impersonate: 4.0.0 - integration_mastodon: 5.1.0 - integration_openai: 4.3.1 - logreader: 6.0.0 - lookup_server_connector: 1.21.0 - mail: 5.7.10 - memories: 8.0.1 - news: 28.1.0 - nextcloud_announcements: 5.0.0 - notes: 4.13.1 - notifications: 6.0.0 - notify_push: 1.3.1 - oauth2: 1.21.0 - ocs_api_viewer: 1.0.11 - password_policy: 5.0.0 - passwords: 2026.3.21 - photos: 6.0.0 - previewgenerator: 5.13.0 - privacy: 5.0.0 - profile: 1.2.0 - provisioning_api: 1.23.0 - recommendations: 6.0.0 - related_resources: 4.0.0 - richdocuments: 10.1.2 - richdocumentscode: 25.4.904 - serverinfo: 5.0.0 - settings: 1.16.0 - sharebymail: 1.23.0 - sharereview: 2.1.0 - spreed: 23.0.3 - suspicious_login: 11.0.0 - systemtags: 1.23.0 - tables: 2.0.1 - text: 7.0.0 - theming: 2.8.0 - thesearchpage: 2.1.2 - twofactor_backupcodes: 1.22.0 - twofactor_totp: 15.0.0 - twofactor_webauthn: 2.6.0 - updatenotification: 1.23.0 - user_status: 1.13.0 - viewer: 6.0.0 - weather_status: 1.13.0 - webhook_listeners: 1.5.0 - whiteboard: 1.5.7 - workflow_script: 4.0.0 - workflowengine: 2.15.0 Disabled: - encryption: 2.21.0 (installed 2.20.0) - files_external: 1.25.1 (installed 1.24.0) - firstrunwizard: 6.0.0 (installed 5.0.0-dev.0) - support: 5.0.0 (installed 4.0.0-dev.0) - survey_client: 5.0.0 (installed 1.8.0) - testing: 1.23.0 - twofactor_nextcloud_notification: 7.0.0 (installed 5.0.0) - user_ldap: 1.24.0 (installed 1.23.0) root@30-Nextcloud:/home/itsupport#
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the repeated client-push synchronization described in the issue, with client push enabled and disabled, and review the linked troubleshooting report for context. The issue does not name a source file or test and leaves expected behaviour unspecified, so a maintainer should first define the notification behaviour and diagnostic evidence needed before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100