Author Topic: Letsencrypt cert bug  (Read 645 times)

spicer

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
    • ltspiceusers.ch
Letsencrypt cert bug
« on: March 27, 2024, 07:57:19 am »
When trying to use a letsecrypt certificate, it gets issued only for the main domain, all my subdomains remain using the self signed certificate. Here's the letsencrypt.log.

PS:
Pls register the user Andy. He waits a long time ;)
« Last Edit: March 27, 2024, 09:08:24 am by spicer »
Translator for german EHCPforce

earnolmartin

  • Administrator
  • Sr. Member
  • *****
  • Posts: 307
    • View Profile
Re: Letsencrypt cert bug
« Reply #1 on: March 30, 2024, 11:36:55 pm »
Subdomains are covered by default unless there's some kind of DNS issue. 

If you could explain how to reproduce this issue, I'll look into it further.

Andy may have to re-register.  Spammers were signing up, so most accounts awaiting approval were deleted.

spicer

  • Jr. Member
  • **
  • Posts: 72
    • View Profile
    • ltspiceusers.ch
Re: Letsencrypt cert bug
« Reply #2 on: March 31, 2024, 06:13:23 am »
I've just added my domain, enabled letsencrypt and then added a subdomain. It also does't work when removing and re-enable letsencrypt after I've added a subdomain. You can see the errors I get within the letsencrypt.log. I don't know how to solve this by myself. I've done all the DNS checks and so far everything seems perfectly fine.
Translator for german EHCPforce

earnolmartin

  • Administrator
  • Sr. Member
  • *****
  • Posts: 307
    • View Profile
Re: Letsencrypt cert bug
« Reply #3 on: June 11, 2024, 10:40:56 pm »
I've just added my domain, enabled letsencrypt and then added a subdomain. It also does't work when removing and re-enable letsencrypt after I've added a subdomain. You can see the errors I get within the letsencrypt.log. I don't know how to solve this by myself. I've done all the DNS checks and so far everything seems perfectly fine.

Sorry it took me so long, but I setup a new test server and setup the DNS to resolve for a test domain (technically a subdomain) provided by https://dynamix.run.  After adding my domain to the panel, I enabled Let's Encrypt.  That worked fine.  I then created a sub-domain on the sub-domain.  Upon loading the sub-domain, it too was now encrypted with a valid Let's Encrypt SSL Certificate.  If your DNS isn't resolving properly / the subdomain doesn't resolve to the same server IP that is making the request for the certificate, it will not work.  Usually, any errors are clearly written to the Let's Encrypt log file.  Please attach your Let's Encrypt log file that contains the errors.

It appears the panel is working properly / intended from the dedicated testing of this scenario I performed tonight... as long as everything is configured properly, of course.