This category is for general issues(=something is broken) regarding YunoHost, NOT apps.
on
This form is written in English but feel free to write in French if you’re more comfortable!
on
What type of hardware are you using
Old laptop or computer
What YunoHost version are you running
12.1.40
How are you able to access your server
The webadmin
SSH
Direct access via physical keyboard/screen
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?
no
Describe your issue
Hello yunoworld !
After doing the last update to 12.1.41 (see the log) I got several warning about /.well-known/ files being modified manually.
I guess these files have been created when I set up the letsencrypt cert, so to me they have not been modified manually.
This warning seems normal to me and it is probably there just to inform me that the letsencrypt config won’t get broken.
However, just need to be sure : someone could confirm that ?
Après avoir fait la dernière mise à jour vers la 12.1.41, j’ai eu des messages d’avertissement sur les fichiers /var/www/.well-known/… qui a été modifié manuellement et ne sera pas mis à jour. Je n’ai pas modifié manuellement ces fichiers, je suppose que c’est l’autoconfig de mise en place des certificats letsencrypt qui l’a fait.
Je voulais m’assurer que cet avertissement peut tranquillement être ignoré. C’est un peu source de confusion.
WARNING Le fichier de configuration '/var/www/.well-known/cloud.maindomain.tld/autoconfig/mail/config-v1.1.xml' a été modifié manuellement et ne sera pas mis à jour
So it’s not related to let’s encrypt, that’s auto configuration files for email to let for example thunderbird autoconfigure your mailbox.
Run the command of jarod to see if something has changed or not.
WARNING Le fichier de configuration '/var/www/.well-known/grist.mydomain.tld/autoconfig/mail/config-v1.1.xml' a été modifié manuellement et ne sera pas mis à jour
WARNING Le fichier de configuration '/var/www/.well-known/snappy.mydomain.tld/autoconfig/mail/config-v1.1.xml' a été modifié manuellement et ne sera pas mis à jour
WARNING Le fichier de configuration '/var/www/.well-known/cloud.mydomain.tld/autoconfig/mail/config-v1.1.xml' a été modifié manuellement et ne sera pas mis à jour
SUCCESS La configuration aurait dû être mise à jour pour la catégorie 'dnsmasq'
dnsmasq:
applied:
/etc/dnsmasq.d/spamhaus:
diff: @@ -4,12 +4,12 @@
# We pick one of spamhaus' a/b/c/d/e nameservers, cf https://multirbl.valli.org/detail/zen.spamhaus.org.html
# And kind of hard-code the corresponding IPs because in practice dnsmasq doesn't allow to have a domain name for the resolver part of server= :| ...
# Fun-fact : did you know that AAAA is the name of IPv6 DNS records, but also the sound you make when debugging network and DNS??? #TheMoreYouKnow
-server=/*.zen.spamhaus.org/185.15.20.108
-server=/*.zen.spamhaus.org/208.85.20.147
+server=/*.zen.spamhaus.org/147.102.226.131
+server=/*.zen.spamhaus.org/185.82.216.38
server=/*.zen.spamhaus.org/213.81.185.73
+server=/*.zen.spamhaus.org/217.12.210.137
server=/*.zen.spamhaus.org/2a00:12a8:8000::fff0:3
server=/*.zen.spamhaus.org/2a05:9404::e0
server=/*.zen.spamhaus.org/2a05:f480:2000:1246:9998:cf46:6cf8:1e7a
-server=/*.zen.spamhaus.org/2a05:f480:2800:129f:da1e:3a4f:abe5:3481
server=/*.zen.spamhaus.org/70.34.211.66
server=/*.zen.spamhaus.org/82.118.21.219
status: updated
pending:
nginx:
applied:
pending:
/var/www/.well-known/cloud.mydomain.tld/autoconfig/mail/config-v1.1.xml:
diff: @@ -1,19 +0,0 @@
-<clientConfig version="1.1">
- <emailProvider id="cloud.mydomain.tld">
- <domain>cloud.mydomain.tld</domain>
- <incomingServer type="imap">
- <hostname>cloud.mydomain.tld</hostname>
- <port>993</port>
- <socketType>SSL</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </incomingServer>
- <outgoingServer type="smtp">
- <hostname>cloud.mydomain.tld</hostname>
- <port>587</port>
- <socketType>STARTTLS</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </outgoingServer>
- </emailProvider>
-</clientConfig>
status: modified
/var/www/.well-known/grist.mydomain.tld/autoconfig/mail/config-v1.1.xml:
diff: @@ -1,19 +0,0 @@
-<clientConfig version="1.1">
- <emailProvider id="grist.mydomain.tld">
- <domain>grist.mydomain.tld</domain>
- <incomingServer type="imap">
- <hostname>grist.mydomain.tld</hostname>
- <port>993</port>
- <socketType>SSL</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </incomingServer>
- <outgoingServer type="smtp">
- <hostname>grist.mydomain.tld</hostname>
- <port>587</port>
- <socketType>STARTTLS</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </outgoingServer>
- </emailProvider>
-</clientConfig>
status: modified
/var/www/.well-known/snappy.mydomain.tld/autoconfig/mail/config-v1.1.xml:
diff: @@ -1,19 +0,0 @@
-<clientConfig version="1.1">
- <emailProvider id="snappy.mydomain.tld">
- <domain>snappy.mydomain.tld</domain>
- <incomingServer type="imap">
- <hostname>snappy.mydomain.tld</hostname>
- <port>993</port>
- <socketType>SSL</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </incomingServer>
- <outgoingServer type="smtp">
- <hostname>snappy.mydomain.tld</hostname>
- <port>587</port>
- <socketType>STARTTLS</socketType>
- <authentication>password-cleartext</authentication>
- <username>%EMAILLOCALPART%</username>
- </outgoingServer>
- </emailProvider>
-</clientConfig>
status: modified
Sorry, it’s only in english, but I think autoconfig/mail/config-v1.1.xml generation is buggy.
The file is missing a final “newline” and when the email in/out feature is disabled it is not removed. The left-over then triggers a “manually modified” error.
Oh thanks, so you’re saying that it is a problem with the way yunohost manage the email in the domain section ? Indeed I disabled the mail for all my subdomain.
