The Basics
- Nextcloud Server version (e.g., 29.x.x):
31.0.9
- Operating system and version (e.g., Ubuntu 24.04):
- Operating System: Manjaro Linux
KDE Plasma Version: 6.3.6
KDE Frameworks Version: 6.18.0
Qt Version: 6.9.2
Kernel Version: 6.16.8-1-MANJARO (64-bit)
- Operating System: Manjaro Linux
- Web server and version (e.g, Apache 2.4.25):
Running httpd -v and apachectl -v both give me command not found.
- Reverse proxy and version _(e.g. nginx 1.27.2)
None
- PHP version (e.g, 8.3):
Running php --version gives me command not found.
- Is this the first time you’ve seen this error? (Yes / No):
No
- When did this problem seem to first start?
Within the last month.
- Installation method (e.g. AlO, NCP, Bare Metal/Archive, etc.)
Not sure (been a long time, probably just directly from repos)
- Are you using CloudfIare, mod_security, or similar? (Yes / No)
No
Summary of the issue you are facing:
I have multiple systems that sync to my server. Everything is running fully updated Manjaro OS. My wife was going to start sorting photos on her laptop and we realized that her system isn’t synced. I checked mine and it’s synced fine.
Things I’ve tried:
(1) Rebooting
(2) Logging out of NextCloud
(3) Stopping sync and restarting it
In NextCloud settings on the client it just perpetually shows “Synchronizing files in local folder”. Sometimes (appears like right when I start NextCloud or pause and then start sync) I’ll see something like 0 of
Steps to replicate it (hint: details matter!):
-
Synchronizing fails every time I run NextCloud desktop client on this system. Not sure what triggered it to start.
Log entries
Looks like it’s claiming the sync is successful (it definitely isn’t). These are from the last lines on my sync log from client (Pictures_Sync.log located in ~./local/share/NextCloud
#=#=#=# Syncrun finished 2025-09-10T00:25:35Z (last step: 11702 msec, total: 12161 msec)
#=#=#=# Syncrun started 2025-09-10T00:26:05Z
#=#=#=#=# Propagation starts 2025-09-10T00:26:06Z (last step: 633 msec, total: 633 msec)
#=#=#=# Syncrun finished 2025-09-10T00:26:06Z (last step: 7 msec, total: 640 msec)
#=#=#=# Syncrun started 2025-09-10T00:30:06Z
#=#=#=# Syncrun finished 2025-09-10T00:33:52Z (last step: 225982 msec, total: 225982 msec)
#=#=#=# Syncrun started 2025-09-10T00:35:01Z
#=#=#=# Syncrun started 2025-09-19T16:37:59Z
#=#=#=# Syncrun started 2025-09-25T20:02:42Z
#=#=#=# Syncrun started 2025-09-30T23:41:07Z
#=#=#=# Syncrun started 2025-10-10T16:09:02Z
#=#=#=# Syncrun started 2025-10-17T00:54:25Z
#=#=#=# Syncrun started 2025-10-21T03:30:53Z
#=#=#=# Syncrun started 2025-10-21T13:24:38Z
#=#=#=# Syncrun started 2025-10-21T13:32:07Z
#=#=#=# Syncrun finished 2025-10-21T13:34:46Z (last step: 158863 msec, total: 158863 msec)
#=#=#=# Syncrun started 2025-10-21T13:36:33Z
#=#=#=# Syncrun finished 2025-10-21T13:43:16Z (last step: 403419 msec, total: 403419 msec)
#=#=#=# Syncrun started 2025-10-21T13:43:48Z
#=#=#=# Syncrun finished 2025-10-21T13:45:16Z (last step: 88552 msec, total: 88552 msec)
#=#=#=# Syncrun started 2025-10-21T13:45:31Z
#=#=#=# Syncrun finished 2025-10-21T13:57:23Z (last step: 711963 msec, total: 711963 msec)
#=#=#=# Syncrun started 2025-10-21T13:58:20Z
#=#=#=# Syncrun finished 2025-10-21T14:11:10Z (last step: 770269 msec, total: 770269 msec)
#=#=#=# Syncrun started 2025-10-21T14:11:55Z
#=#=#=# Syncrun finished 2025-10-21T19:31:03Z (last step: 19148137 msec, total: 19148137 msec)
#=#=#=# Syncrun started 2025-10-21T19:32:03Z
Nextcloud
Please provide the log entries from your Nextcloud log that are generated during the time of problem (via the Copy raw option from Administration settings->Logging screen or from your nextcloud.log located in your data directory). Feel free to use a pastebin/gist service if necessary.
From what I can see, there are no logs (see screenshot below) from the relevant period of time. I had a couple of missed logins but nothing about syncing. It's currently 4:26pm, I just did an attempt to force sync, and last log is from bad login attempt hours ago.
I tried locating nextcloud.log but couldn’t find the right one.
Tips for increasing the likelihood of a response
- Use the
preformatted textformatting option in the editor for all log entries and configuration output. - If screenshots are useful, feel free to include them.
- If possible, also include key error output in text form so it can be searched for.
- Try to edit log output only minimally (if at all) so that it can be ran through analyzers / formatters by those trying to help you.
