Letsencrypt not working on one site

Discussion in 'ISPConfig 3 Priority Support' started by unsichtbare, Oct 29, 2024.

Tags:
  1. unsichtbare

    unsichtbare Member HowtoForge Supporter

    I have my server on a DMZ (NAT'ed) and I have turned off Letsencrypt check in server settings.
    Site: https://vmsources.com will not create certificate after migration to new server
    Sites: https://support.vmsources.com and https://share.vmsources.com created certificates
    Sites are not created as sub-domains, rather A-records exist for each and each is an individual site in ISPconfig.
    Also, there does not seem to be a Letsencrypt log file anywhere
    Code:
    root@web1:/var/log/ispconfig# find / -name letsencrypt.log
    root@web1:/var/log/ispconfig#
    
    THX in adv.
    -John
     
  2. unsichtbare

    unsichtbare Member HowtoForge Supporter

    When I create a self-signed certificate, the site loads. It just seems to be Letsencrypt.
    Site now reverted to old server until I can figure out.
    THX,
    -John
     
  3. till

    till Super Moderator Staff Member ISPConfig Developer

    unsichtbare likes this.
  4. unsichtbare

    unsichtbare Member HowtoForge Supporter

    Thank you for pointing me at the FAQ, especially in locating the relevant log files. I have verified all items on the FAQ as correct, however one site is still not able to get a Letsencrypt SSL. It is somehow coming up with the old server IP (38.99.70.248) for the site after DNS is changed and several hours passed:
    Code:
    [Wed Oct 30 02:18:08 PM UTC 2024] errordetail='38.99.70.248: Invalid response from http://www.vmsources.com/.well-known/acme-challenge/iTOhuAS_Luk_sdgsdhsfhsfhsfghsfghfshdfhgdhssghshshswbvc: 404'
    [Wed Oct 30 02:18:08 PM UTC 2024] www.vmsources.com: Invalid status. Verification error details: 38.99.70.248: Invalid response from http://www.vmsources.com/.well-known/acme-challenge/iTOhuAS_Luk_sdgsdhsfhsfhsfghsfghfshdfhgdhssghshshswbvc: 404
    My question is where is this IP cached or coming from? I have grep'ed and attempted to locate it but I cannot.
    THX,
    -John
     
  5. unsichtbare

    unsichtbare Member HowtoForge Supporter

    OK, resolved. It was DNS /auto sub-domain www.
     
  6. till

    till Super Moderator Staff Member ISPConfig Developer

    Changing an IP in DNS might take up to 24 hours. This is cached on the resolving DNS servers used by your server, so it's not cached on your server.
     

Share This Page