Posts by oekowalti

    I have a problem with one certificate of one domain: "". [All other domains are full working.]

    The backend shows me the Status Ok for this certificate, but in all browsers the same error is reasing:

    I tryed to deactivate letsencrypt, made a self signed cert and after that I activated letsencrypt again. But I have allways the same erros.

    Also after having updated the plugin letsencrypt to the new version 1.1.0, I made the same procedures mentioned above one again. But I have still the same erros :( .

    Is it possible, that an old certificate is blocking the procedure on creating new certs? If this is true, can I delete manualy this bad cert to force the system on creating a new cert? Where do I so?

    For such cases, I think it would be helpfull, if the plugin letsencrypt shows a button, to erase all old files and to begin new concerning certificates for a specific domain.


    The log shows:

    1. [Sat Jul 23 07:10:48 2016] [debug] Modules::Plugin::_call: Calling run() method on Plugin::LetsEncrypt
    2. [Sat Jul 23 07:10:48 2016] [debug] iMSCP::Execute::execute: certbot-auto revoke --no-self-upgrade --text --agree-tos --non-interactive --verbose --cert-path /var/www/imscp/gui/data/certs/
    3. [Sat Jul 23 07:10:49 2016] [debug] iMSCP::Execute::getExitCode: Command exited with value: 2
    4. [Sat Jul 23 07:10:50 2016] [error] Plugin::LetsEncrypt::run: usage:
    5. certbot-auto [SUBCOMMAND] [options] [-d domain] [-d domain] ...
    6. letsencrypt: error: argument --cert-path: No such file or directory

    Now, I see, that the file in the cert-path is missing.
    As next step, I copied an other cert to a new file with the missing name.
    Now I run the pending requests in the debugger interface again. After that all works fine:

    Thank you very much for your usefull help :) .
    Have a good weekend!

    Die Domain "" war früher als alias domain mit einem letsencrypt zertifikat ausgestattet. Dann löschte ich diesen alias und erstellte eine neue (Haupt-) Domain unter dem gleichen Namen.

    Nun erhalte ich diese Statusmeldung X( :

    Leider kann ich jetzt das Zertifikat auch nicht manuell einfügen und auch eine Deaktivierung ist nicht möglich.

    I have daily the following email-message:

    1. Server IP:
    2. Version: 1.3.0
    3. Build: 20160626
    4. Message severity: error
    5. An error has been raised while executing function main::run in/var/www/imscp/engine/backup/imscp-backup-all:
    6. iMSCP::Database::mysql::dumpdb: mysqldump: Got error: 1449: The user specified as a definer ('root'@'localhost') does not exist when using LOCK TABLES

    OS is debian 8.0, all packages on newest versions.

    Yes, I made letsencrypt certs in the past by command line.
    Can you integrate into the plugin, that old certs are deleted in the next version?

    I have deleted the files as you mentionend above for the second wrong domain an rerun the again. After that, the cert for the domain was created perfectly.

    Thank you very much for your help!