Android: spammed with conflict notifications for old pictures


Nextcloud version (eg, 20.0.5):
Operating system and version (eg, Ubuntu 20.04): Raspberry Pi OS 11
Nextcloud runs in Docker on this system.

The issue you are facing:
Since this morning, my phone gets spammed by the Nextcloud app with notifications of file conflicts for pictures previously sync’d via the automatic upload function. I’ve not touched the files on the server or through any client. If I discard the notifications, they keep coming back later. I would need to click each file and keep one of the (identical) copies, but it seems the more I click, the more it brings, and there’s hundreds and hundreds of pictures on the server.
This started this morning, I found the first notifications upon waking up.

Is this the first time you’ve seen this error? (Y/N): Y

Steps to replicate it:

  1. Wake up
  2. Pick up phone :frowning:

The output of your Nextcloud log in Admin > Logging:
The only logs for the last few days are from the secrets app, which should not be relevant here.

The output of your config.php file in /path/to/nextcloud (make sure you remove any identifiable information!):
From the container:

$CONFIG = array (
  'memcache.local' => '\\OC\\Memcache\\APCu',
  'datadirectory' => '/data',
  'instanceid' => 'EDITED',
  'passwordsalt' => 'EDITED',
  'secret' => 'EDITED',
  'trusted_domains' =>
  array (
    0 => 'EDITED',
  'dbtype' => 'sqlite3',
  'version' => '',
  'overwrite.cli.url' => 'https://EDITED',
  'installed' => true,
  'enforce_theme' => '',
  'mail_from_address' => 'pierric',
  'mail_smtpmode' => 'smtp',
  'mail_sendmailmode' => 'smtp',
  'mail_domain' => 'EDITED',
  'mail_smtphost' => 'EDITED',
  'mail_smtpport' => '465',
  'mail_smtpauthtype' => 'LOGIN',
  'mail_smtpauth' => 1,
  'mail_smtpname' => 'pierric',
  'mail_smtppassword' => 'EDITED',
  'maintenance' => false,
  'theme' => '',
  'loglevel' => 2,
  'filelocking.enabled' => 'true',
  'memcache.locking' => '\\OC\\Memcache\\APCu',
  'mail_smtpsecure' => 'ssl',

The output of your Apache/nginx/system log in /var/log/____:
In the container there is an error.log file but it is empty.

Output errors in nextcloud.log in /var/www/ or as admin user in top right menu, filtering for errors. Use a pastebin service if necessary.
There is no such file in the container, and I’m not sure what menu item is being referred to here…

In addition, I see in the docker logs the following 2 lines, however they are already 2 days old so probably not relevant:

2023-09-17T00:00:00.073925614Z error: failed to rename /config/log/nginx/access.log to /config/log/nginx/access.log.1: Permission denied
2023-09-17T00:00:00.074935551Z error: failed to rename /config/log/php/error.log to /config/log/php/error.log.1: Permission denied
1 Like

/me thinks, the owner of the files or the filesystem ist not www-data.
It should be.
Just a guess from the apache logfiles…

docker chown …


There is no www-data user in /etc/passwd inside the container. There’s abc and nginx. The picture files in the /data/pierric/files/Photos/Phone/2023/09/ folder, where uploads get sent, all belong to abc:users (1000:1000).

Also, I found the option to “skip uploading” instead of “ask me every time” in the auto-upload configuration in the app, and selected that as a temporary workaround. Yet, the notifications are still coming back!

EDIT: note that I’m using the Docker container from the LinuxServer team (in case there is ambiguity)

1 Like

The constant notifications waking my phone up was stressing me out so I cleared the data from the app and reconfigured the auto-upload from scratch, this time selecting “skip upload” from the get-go. I will revert here in a while and share whether this has stopped the issue or not.

Surprisingly, while I was doing this, the server got slower and slower and then the container just crashed. After it restarted it’s working as usual. There’s only a “suspicious login” entry in the Logging page, which matches my IP, and corresponds to my logging back in from the phone, so probably nothing to worry about on that front.

1 Like

If this started after upgrading the client to v3.26.0 it might be related to this currently mysterious issue: