let's encrypt fehler

  • i-mscp 1.3.16 / Let’s Encrypt 2.0.5


    Fehler :


    wäre nett wenn da zeit nah eine Lösung gibt da das Zertifikat heute abläuft und ein paar andere in den nächten Tagen

  • @fan-com


    Can I access the server?

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206

  • @fan-com


    Fixed as follow:


    Code
    1. # certbot-auto renewUpgrading certbot-auto 0.9.3 to 0.11.1...Replacing certbot-auto...Creating virtual environment...Installing Python packages...Installation succeeded.Saving debug log to /var/log/letsencrypt/letsencrypt.log-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/podoprax.at.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/medikon-oberhausen.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/podoprax.ch.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/stenger-goldankauf-saarland.de-0001.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/podoprax.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/stenger-goldankauf.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/stenger-goldankauf-sulzbach.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/wiki.podoprax.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/stenger-goldankauf-saarland.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/kulttempel-tickets.de.conf-------------------------------------------------------------------------------Cert not yet due for renewal-------------------------------------------------------------------------------Processing /etc/letsencrypt/renewal/fan-com.de.conf-------------------------------------------------------------------------------Cert is due for renewal, auto-renewing...Renewing an existing certificatePerforming the following challenges:http-01 challenge for fan-com.dehttp-01 challenge for www.fan-com.deWaiting for verification...Cleaning up challengesGenerating key (2048 bits): /etc/letsencrypt/keys/0017_key-certbot.pemCreating CSR: /etc/letsencrypt/csr/0017_csr-certbot.pem-------------------------------------------------------------------------------new certificate deployed without reload, fullchain is/etc/letsencrypt/live/fan-com.de/fullchain.pem-------------------------------------------------------------------------------The following certs are not due for renewal yet:/etc/letsencrypt/live/podoprax.at/fullchain.pem (skipped)/etc/letsencrypt/live/medikon-oberhausen.de/fullchain.pem (skipped)/etc/letsencrypt/live/podoprax.ch/fullchain.pem (skipped)/etc/letsencrypt/live/stenger-goldankauf-saarland.de-0001/fullchain.pem (skipped)/etc/letsencrypt/live/podoprax.de/fullchain.pem (skipped)/etc/letsencrypt/live/stenger-goldankauf.de/fullchain.pem (skipped)/etc/letsencrypt/live/stenger-goldankauf-sulzbach.de/fullchain.pem (skipped)/etc/letsencrypt/live/wiki.podoprax.de/fullchain.pem (skipped)/etc/letsencrypt/live/stenger-goldankauf-saarland.de/fullchain.pem (skipped)/etc/letsencrypt/live/kulttempel-tickets.de/fullchain.pem (skipped)Congratulations, all renewals succeeded. The following certs have been renewed:/etc/letsencrypt/live/fan-com.de/fullchain.pem (success)
    SQL
    1. # mysql -u debian-sys-maint -p<password>> USE imscp;> UPDATE letsencrypt SET letsencrypt_status = 'torenew';> \q


    Shell-Script
    1. # perl /var/www/imscp/engine/imscp-rqst-mngr -v


    Note that only SSL certificate of fan-com.de was due for renewal:


    BTW: The error you showed above shouldn't occurs. However because your server is a HOME server and because traffic is really slow (including connections), this could explain the problem.

    badge.php?id=1239063037&bid=2518&key=1747635596&format=png&z=547451206