Info: The operation ‘Install Let’s encrypt certificate on ‘nuage.ndd.fr’ domain’ has failed! To get help, please share the full log of this operation using the command ‘yunohost log display 20190708-125831-letsencrypt_cert_install-nuage.ndd.fr --share’
Me too… I can’t reach my server anymore
First time is happen with Yunohost !
I can’t access to my server even on ssh…
Is there another way to connect to my kimsufi server to get the last backup ?
When I look at Kimsufi monitoring, I see the 5 processes using more RAM as usual : fail2ban, Matrix, coturn, php-fpm, mysqld
So the server is running, probably a certificate problem what Riot and Nextcloud client are telling me when I try to connect them to my server.
Du coup problème de hercut plus ou moins résolu ( cc AAleks_ )
For whatever reason, after the update nginx was trying to find a certificate for tld.fr instead of using subdomain.tld.fr as configured. This might be of interest to other people who have only configured a TLD.
(bien sûr, ajuster les xxxxx et les deux(subdomain).ndd.fr)
A few words in English as well:
The problem was solved using a self-signed certificate that was already generated for the subdomain, but not the domain itself. Even though the domain was not configured in Yunohost, nginx was looking for a certificate for it and failling to start as it didn’t find one:
Jul 08 10:18:32 nuage.ndd.fr nginx: nginx: [emerg] BIO_new_file("/etc/yunohost/certs/ndd.fr/crt.pem") failed (SSL: error:02001002:system library:fopen:No such file or directory
Jul 08 10:18:32 nuage.ndd.fr nginx: nginx: configuration file /etc/nginx/nginx.conf test failed
L’installation d’une app ne devrait pas non plus toucher au certificats … Ce qui aurait été intéressant de voir, c’est vers quoi pointait le lien symbolique avant de le changer, ce qui aurait pu aidé à comprendre le problème…