Viestit paikassa Nextcloud

As a workaround, adding –no-warnings seems to suppress this output.

12. huhtikuuta 2024 klo 10.21
Sijainti: Vianhallintajärjestelmät: Github

As a workaround, adding --no-warnings seems to suppress this output.

Vastaa viestiin sen kontekstissa (Github)

I just tested uploading from the Nextcloud app, and it is similarly affected

12. marraskuuta 2023 klo 17.29
Sijainti: Vianhallintajärjestelmät: Github

I just tested uploading from the Nextcloud app, and it is similarly affected: no conflict dialog is shown and the existing file gets overwritten.

Vastaa viestiin sen kontekstissa (Github)

Existing files with ”ä” in the filename are silently overwritten when a new file with the same name is uploaded

12. marraskuuta 2023 klo 11.09
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Apple

Steps to reproduce

  1. Have a PDF file with the name ”ä.pdf” (sic) in your Nextcloud.
  2. Have a different PDF file with the same name on your IOS device (Files app).
  3. Choose to share the file from your IOS device to Nextcloud.
  4. Select the folder where ”ä.pdf” already exists.
  5. Upload.

Expected behaviour

Get a dialog to choose how to deal with the filename conflict.

Actual behaviour

No dialog. The the existing file is silently overwritten by the newly shared file.


Nothing in server logs, but here’s the app log (at the default level).

Reasoning or why should it be changed/implemented?

The issue leads to data loss. I discovered this when I realized that saving bills from my banking app by sharing them to my Nextcloud had been doing this for who knows how long. (My electricity bills have the service provider name, ”Oulun Energia Sähköverkko Oy” in their filename.)

Environment data

iOS version: 17.0.3

Nextcloud iOS app version: ”Nextcloud Liquid for iOS”

Server operating system:

Web server: Apache 2.4.41

Database: MySQL/MariaDB 10.3.38

PHP version: 8.2

Nextcloud version:


  • This is not reproducible on Android (with my server), which is why I’m pretty sure the fault lies with the IOS app.
  • Also not reproducible on IOS with filenames with ASCII-only names (FWICT); this general case was apparently fixed when first reported as Upload via Share Menu Silently Overwrites Existing Files #1737.

Vastaa viestiin sen kontekstissa (Github)

25.0.3 (as indicated by output from `occ –version` above).

25. tammikuuta 2023 klo 15.01
Sijainti: Vianhallintajärjestelmät: Github

25.0.3 (as indicated by output from `occ –version` above).

Vastaa viestiin sen kontekstissa (Github)

The exit code issue is still there

25. tammikuuta 2023 klo 14.04
Sijainti: Vianhallintajärjestelmät: Github

The exit code issue is still there:

# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ --version
Nextcloud 25.0.3
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ files:scan -- nonexistantuser
Unknown user 1 nonexistantuser
| Folders | Files | Elapsed time |
| 0       | 0     | 00:00:00     |
# echo $?

Vastaa viestiin sen kontekstissa (Github)

Still present in Nextcloud 3.21.2

1. lokakuuta 2022 klo 18.46
Sijainti: Vianhallintajärjestelmät: Github
Avainsanat: Android, Samsung

Still present in Nextcloud 3.21.2. My device is a Samsung A9 running Android 10.

Vastaa viestiin sen kontekstissa (Github)

I tested the appimage and the issue still reproduces.

10. syyskuuta 2022 klo 19.58
Sijainti: Vianhallintajärjestelmät: Github

Hi @claucambra, I tested the appimage and the issue still reproduces.

Vastaa viestiin sen kontekstissa (Github)

Using a path with umlauts as logDir is broken

4. syyskuuta 2022 klo 14.52
Sijainti: Vianhallintajärjestelmät: Github

Bug description

Using a path with umlauts as logDir causes an incorrectly encoded directory to be created and used as log directory, instead of the specified directory.

Steps to reproduce

  1. Quit the client.
  2. Edit nextcloud.cfg. Set logDir=/home/jani/Tänne (applying appropriately to your home directory)
  3. Start the client.
  4. ls /home/jani/Tänne

Expected behavior

A listing of new log files residing in /home/jani/Tänne.

Which files are affected by this bug

This question is unclear. The log files are the ones affected.

Operating system


Which version of the operating system you are running.

Ubuntu 20.04


Distro package manager

Nextcloud Server version


Nextcloud Desktop Client version


Is this bug present after an update or on a fresh install?

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

  •  Default internal user-backend
  •  LDAP/ Active Directory
  •  SSO – SAML
  •  Other

Nextcloud Server logs

No response

Additional info

This bizarre and otherwise exhaustingly long issue form is lacking a ”What happens instead of my expected outcome” question, so I’m entering it here instead: there are no logs in the specified target directory (it doesn’t even exist if you’ve not created it beforehand). Instead, like in the ye olden days, there is now a directory called Tänne containing the logs. In nextcloud.cfg the path has been re-encoded as logDir=/home/jani/T\xc3\xa4nne/ which is apparently how it should be, since a similarly re-encoded value for a ...localPath with umlauts in the [accounts] section has been working just fine for as long as I can remember using it.

Vastaa viestiin sen kontekstissa (Github)

check_data_directory_permissions allows the admin to turn off the automatic permissions reset

10. tammikuuta 2019 klo 13.48
Sijainti: Keskustelupalstat: Nextcloud
Avainsanat: turvallisuus

Sorry for necromancing, but because Google seems to like this thread, I just thought I’d add a mention that a check_data_directory_permissions option for config.php has since been implemented (and backported down to NC12), and it allows the admin to turn off the automatic permissions reset (by assigning it false).

This is discouraged however, and ACLs or other means of managing access are still the better option where available.

Vastaa viestiin sen kontekstissa (Nextcloud)

Looks like it waits a fixed 30 minutes before letting you run it again

30. maaliskuuta 2017 klo 20.58
Sijainti: Keskustelupalstat: Nextcloud
Avainsanat: SQL

Looks like it waits a fixed 30 minutes before letting you run it again. You can either wait it out (as you probably have by now) or, if you’re impatient (like me) and really sure it’s not running already, `SELECT * FROM ’oc_appconfig’ WHERE ’configkey’ LIKE ’lastActivity’` and delete that timestamp.

Vastaa viestiin sen kontekstissa (Nextcloud)

Vanhempia »