Création d'un rapport de bogue ou d'un problème :
paste -sd '' /DietPi/dietpi/.version. 6.11echo $G_DISTRO_NAME ou cat /etc/debian_version.uname -a.echo $G_HW_MODEL_DESCRIPTION EG : RPi3Renseignements supplémentaires (s'il y a lieu) :
dietpi-bugreport ID>>le numéro.
Que DEVRAIT-il se passer ? -->
Qu'est-ce qui se passe ? -->
Traduit avec www.DeepL.com/Translator

@ludji49
.well-known folders are added by various web services and scripts, nothing to worry about.
Simply move it outside your Nextcloud folder and inside again after update has finished:
mv /path/to/nextcloud/.well-known /tmp/
Update Nextcloud via web updater
mv /tmp/.well-known /path/to/nextcloud/
I just don't understand moving out of your Nextcloud folder and inside
With the cmd putty
@ludji49
mv /path/to/nextcloud/.well-known /tmp/mv /tmp/.well-known /path/to/nextcloud/there is an error on the writing of the command

@ludji49
Ah sorry, /path/to/nextcloud/ should be replaced with the path to your nextcloud directory. On DietPi it should be then:
mv /var/www/nextcloud/.well-known /tmp/
and after Nextcloud update: mv /tmp/.well-known /var/www/nextcloud/
Update done, but for the next update I have to go through this command
mv /var/www/nextcloud/.well-known /tmp/
and after Nextcloud update: mv /tmp/.well-known /var/www/nextcloud/

@ludji49
That's true.
One of the negative sides of having webroot within /nextcloud directory. Other software tends to place file into webroot, which Nextcloud then identifies as integrity check violation. They already added much of the "well known" files/folders to be excluded for this, but for some reason .well-known still breaks updates.
You could check what is inside and if it's needed: ls -al /var/www/nextcloud/.well-known
Thank you very much .......
I mark this as closed, as initial issue is answered/solved. Please reopen, if required.