I'm having an error in lets encrypt.

Discussion in 'HOWTO-Related Questions' started by Mateus Takz, May 22, 2017.

  1. Mateus Takz

    Mateus Takz New Member

    I have a problem with LETS ENCRYPT, the first domain created, installed and completed successfully and is working with http and https, all ok. In the second domain I did the same procedure and it failed to generate the certificate, so it blocked the apache and did not allow to upload the service, so I deleted / etc / apache2 / sites-available / in part <VirtualHost *: 443>, Then Apache come back the service to work.

    Remember that I have only a static public IP. My intention is to enable ssl in all my domains.

    My question is how can I clean up any files created with failure and how to fix this problem.
  2. sjau

    sjau Local Meanie Moderator

    would be good if you could post the according vhost file and also the the ssl folder for that domain. Also error logs from apache when it can't restart would be great.
  3. Turbanator

    Turbanator Member HowtoForge Supporter

    also check the letsencrypt.log since that will tell if any issue during cert. Seems strange that a failed LE would cause an apache2 issue, so my guess is something else is wrong, like maybe a directive issue.
  4. ahrasis

    ahrasis Well-Known Member HowtoForge Supporter

    It is normal rather than strange to me. You can also check your vhost folder for the related vhost and its err files. My observation is that some new vhost files created might be using non ISPC LE symlink which caused apache not restarting. This is due to creating some LE certs during certbot / LE installation, which one shouldn't do, unless he really knows what he was doing.

Share This Page