Lets encrypt SSL on a subdomain made by creating a new website?

Discussion in 'General' started by smokinjo, Feb 27, 2020.

  1. smokinjo

    smokinjo Member HowtoForge Supporter

    I created a subdomain by the method suggested by Til, whcih is just creating a new website that includes the subdomain of an existing domain on the server.
    Will using lets encrypt successfully be able to create a SSL certificate, since it is already used by the main domain?
    I added the lets encrypt to my new site and 6 hour slater, the site is still not SSL encrypted. It is still activated, so it did not fail. What is the normal delay frm the time it is turned on to when the site is encrypted?

    Thanks

    Joseph
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    yes

    1-2 minutes. If LE got deactivated, then follow the Let's encrypt error FAQ post to find out why.
     
  3. smokinjo

    smokinjo Member HowtoForge Supporter

    Hello
    It seems that I have an error in the log files. Here is the partbpf the most recent logs to show the errors. It sems that the domain with the issues is having an error. Thansk for feedbak.

    Joseph


    2020-02-27 17:42:48,170:WARNING:certbot.renewal:renewal config file {} is missing a required file reference
    2020-02-27 17:42:48,170:WARNING:certbot.renewal:Renewal configuration file /etc/letsencrypt/renewal/mmaj.ca.conf is broken. Skipping.
    2020-02-27 17:42:48,187:DEBUG:certbot.renewal:Traceback was:
    Traceback (most recent call last):
    File "/usr/lib/python2.7/dist-packages/certbot/renewal.py", line 59, in _reconstitute
    renewal_candidate = storage.RenewableCert(full_path, config)
    File "/usr/lib/python2.7/dist-packages/certbot/storage.py", line 373, in __init__
    "file reference".format(self.configfile))
    CertStorageError: renewal config file {} is missing a required file reference

    2020-02-27 17:42:48,197:INFO:certbot.renewal:Cert not yet due for renewal
    2020-02-27 17:42:48,215:DEBUG:certbot.main:Exiting abnormally:
    Traceback (most recent call last):
    File "/usr/bin/certbot", line 11, in <module>
    load_entry_point('certbot==0.10.2', 'console_scripts', 'certbot')()
    File "/usr/lib/python2.7/dist-packages/certbot/main.py", line 849, in main
    return config.func(config, plugins)
    File "/usr/lib/python2.7/dist-packages/certbot/main.py", line 655, in renew
    renewal.handle_renewal_request(config)
    File "/usr/lib/python2.7/dist-packages/certbot/renewal.py", line 430, in handle_renewal_request
    len(renew_failures), len(parse_failures)))
    Error: 0 renew failure(s), 1 parse failure(s)
     
  4. smokinjo

    smokinjo Member HowtoForge Supporter

    I just realised that the domain noted the domain that seems to error in th elog is the main domain.
    It does not mention the subdomain, which is th one that I am trying to fix.
    Does this matter? I mean, should I see in the log the subdomain domain in the error, or will it always be the main domain if it errors?

    Thanks

    Joseph
     
  5. till

    till Super Moderator Staff Member ISPConfig Developer

    Yes. The domain is not mentioned in the log as it is not possible to authenticate it at all. What you can try is disabling the let#s encrypt check (if you havent tested that yet as its mentione din the FAQ).
     
  6. smokinjo

    smokinjo Member HowtoForge Supporter

    I seemed to get it working:)

    I was never typing in the https before the domain, and I also did nto force https connections.

    My site is secure:)

    Thanks

    Joseph
     

Share This Page