letsencrypt cert not created for subdomain

Discussion in 'ISPConfig 3 Priority Support' started by atle, Oct 21, 2020.

  1. atle

    atle Member HowtoForge Supporter

    When I add a vhost subdomain, like foo.bar.com, letsencrypt creates the cert for apex, not the subdomain. Have a look at https://hemma.wjk.se
    What am I doing wrong here?
     
  2. Jesse Norell

    Jesse Norell ISPConfig Developer Staff Member ISPConfig Developer

  3. atle

    atle Member HowtoForge Supporter

    Hi, thanks for your reply. A cert is created, but not for the subdomain, it is created for the apex, that is, wjk.se in this case. If you look at the certificate, you will see it is certified to wjk.se.

    But. now when I look at it again, it says the cert is assigned to our generic autoconfig subdomain. I have installed Shaals autmail after I posted the thread.
    Hm, this is starting to get complex, will uninstall automail so this case is clean and nice.
     
  4. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    Go through the FAQ. I think the cert is not issued, but you see the cert of the first domain in the list.
     
  5. atle

    atle Member HowtoForge Supporter

    Yes, you are right, its the first domain that is shown. I re-created the subdomain now, and now the cert is ok. Need to dig in to this further to fully understand.
     
  6. Th0m

    Th0m ISPConfig Developer Staff Member ISPConfig Developer

    When SSL is disabled or there is no valid cert, the first vhost with ssl enabled is selected. That's default apache behaviour.
     

Share This Page