Up !
Pour le password j’ai simplement changé celui-ci à l’issue de la restau.
Par contre les dynDNS font de la résistance : https://paste.yunohost.org/raw/pugosajaho
root@chaton:~# yunohost dyndns subscribe -d chaton.noho.st
Kchaton.noho.st.+165+01451
Success! DynDNS domain registered
Success! DynDNS cron job created
root@chaton:~# yunohost dyndns update
Info: Updated needed, going on...
Outgoing update query:
;; ->>HEADER<<- opcode: UPDATE, status: NOERROR, id: 0
;; flags:; ZONE: 0, PREREQ: 0, UPDATE: 0, ADDITIONAL: 0
;; ZONE SECTION:
;noho.st. IN SOA
;; UPDATE SECTION:
_xmpp-client._tcp.chaton.noho.st. 0 ANY ANY
_xmpp-server._tcp.chaton.noho.st. 0 ANY ANY
muc.chaton.noho.st. 0 ANY ANY
pubsub.chaton.noho.st. 0 ANY ANY
vjud.chaton.noho.st. 0 ANY ANY
xmpp-upload.chaton.noho.st. 0 ANY ANY
*.chaton.noho.st. 0 ANY ANY
chaton.noho.st. 0 ANY ANY
chaton.noho.st. 0 ANY ANY
chaton.noho.st. 0 ANY ANY
mail._domainkey.chaton.noho.st. 0 ANY ANY
_dmarc.chaton.noho.st. 0 ANY ANY
chaton.noho.st. 0 ANY ANY
_xmpp-client._tcp.chaton.noho.st. 3600 IN SRV 0 5 5222 chaton.noho.st.
_xmpp-server._tcp.chaton.noho.st. 3600 IN SRV 0 5 5269 chaton.noho.st.
muc.chaton.noho.st. 3600 IN CNAME chaton.noho.st.
pubsub.chaton.noho.st. 3600 IN CNAME chaton.noho.st.
vjud.chaton.noho.st. 3600 IN CNAME chaton.noho.st.
xmpp-upload.chaton.noho.st. 3600 IN CNAME chaton.noho.st.
*.chaton.noho.st. 3600 IN A xx.xx.xx.xx #IP publique du serveur
chaton.noho.st. 3600 IN CAA 128 issue "letsencrypt.org"
chaton.noho.st. 3600 IN MX 10 chaton.noho.st.
chaton.noho.st. 3600 IN TXT "v=spf1 a mx -all"
mail._domainkey.chaton.noho.st. 3600 IN TXT "v=DKIM1; h=sha256; k=rsa; p=MIG fMA0GCSqGSIb3DQEBAQUAA4GNADCBiQKBgQCpJ5M+sGdsMld3s16hYy7wU/i58FMbUaxWmP41icFD2Am ZrEFyWLlvXYqSj/RqOFEVXNQhRqrqXxrEOb71KvKQ5AgYb5KFqQELj2aqbpyLxNkxzPrBHq92NAi1J4D Ae997UnnZsLFIf2TvAcs/Eed33M/tbEqUH+AYW++OBT6KZwIDAQAB"
_dmarc.chaton.noho.st. 3600 IN TXT "v=DMARC1; p=none"
chaton.noho.st. 3600 IN A xx.xx.xx.xx #IP publique du serveur
; TSIG error with server: tsig indicates error
update failed: NOTAUTH(BADKEY)
Info: The operation 'Update the IP associated with your YunoHost subdomain 'chat on.noho.st'' could not be completed. Please share the full log of this operation using the command 'yunohost log display 20201112-104815-dyndns_update-chaton.no ho.st --share' to get help
Error: Could not update IP address to DynDNS
Pour moi ça ressemble à un soucis de certificat. Du coup je suis repassé à de l’auto-signé avant de réinstaller du Let’s Encrypt :
root@chaton:~# yunohost domain cert-install chaton.noho.st --self-signed --force
Warning: The configuration file '/etc/nginx/conf.d/yunohost_admin.conf.inc' has been manually modified and will not be updated
Warning: The configuration file '/etc/nginx/conf.d/yunohost_api.conf.inc' has been manually modified and will not be updated
Success! Self-signed certificate now installed for the domain 'chaton.noho.st'
root@chaton:~# yunohost domain cert-status
certificates:
chaton.noho.st:
CA_type: Self-signed
summary: WARNING
validity: 3649
root@chaton:~# yunohost domain cert-install chaton.noho.st
Error: The DNS records for domain 'chaton.noho.st' is different from this server's IP. Please check the 'DNS records' (basic) category in the diagnosis for more info. If you recently modified your A record, please wait for it to propagate (some DNS propagation checkers are available online). (If you know what you are doing, use '--no-checks' to turn off those checks.)
root@chaton:~# yunohost dyndns update
Info: No updated needed.
Bon, je vais attendre de voir si c’est bien un soucis de propagation.
Un ping sur chaton.noho.st renvoie toujours l’ancienne IP.
Edith : L’IP est maintenant la bonne, par contre toujours impossible d’installer le certificat let’s encrypt.