Posts by fulltilt

    I use following settings for proftpd TLS

    re-configuration tasks:

    with a new system it seems to work if all certs have been created with the snap certbot kess fix ...

    However, existing LE certs with the old chain are marked as invalid and the apache ssl configs are deleted.

    To avoid the problem you would have to replace all old chain1.pem and fullchain1.pem with the new one:


    does anyone have an idea how to repair the whole thing for all chains under "/etc/letsencrypt/archive/*/" at once?


    maybe a bash script which processes all the subfolders in a loop ...

    it seems we need to use the vege.net fix (OpenSSL.pm line 134) when running i-mscp re-configuration (installer) task ...

    the panel & customer certs are marked as invalid after a i-mscp re-configuration

    Code
    1. [DEBUG] iMSCP::OpenSSL::validateCertificate: error /etc/imscp/imscp_services.pem: verification failed
    2. [DEBUG] iMSCP::LockFile::release: Releasing exclusive lock on /var/lock/imscp.lock
    3. [FATAL] Missing or bad entry found in configuration file.
    4. [ERROR] iMSCP::Dialog::_execute: Failed dialog:

    I have cleaned up some more stuff ... it works now. also with Debian Buster!

    see below


    Undo Fix by vege.net (when in use) and DST Root CA X3 removal

    I've added some more stuff to the snap certbot fix!

    Certbot Fix by kess:

    thanks a lot to: vege.net, kess, Athar, Nuxwin and everyone else who helped & suggested solutions

    I just got a little issue, the "cross-signed" certificate in CA-Certificate, I disabled those, wasn't able to use CURL with sites based on Let'sEncrypt SSL certs.


    Thank you for the details!

    Could you give us a list of the CA certs which have been added & removed?


    on my test VPS this one is still in place

    Code
    1. cat /usr/lib/ssl/certs/2e5ac55d.0