Delete certbot cert

Discussion in 'Installation/Configuration' started by SamTzu, Aug 31, 2018.

  1. SamTzu

    SamTzu Active Member

    I'm having some issues in deleting site certificates.
    When moving a site from old to new server and creating Lets Encrypt SSL cert for the first time on the new server it's a good idea to wait some time. Lets Encrypt server uses some really slow DNS servers (clearly not Google DNS servers that update records every 5min) and this often causes it to generate the SSL cert with the old server/site name.
    I wan't to completely remove the LetsEncrypt SSL certs but so far I have had to do it manually.
    When I remove Let's Encrypt SSL and SSL from ISPconfig site tab it doesn't actually remove anything under /etc/letsencrypt or /var/ww/site-name.com/ssl/

    What is the correct way of "purging" LetsEncrypt files so that I can regenerate them properly from the start?
     
    Last edited: Aug 31, 2018
  2. ahrasis

    ahrasis Well-Known Member

    Simply delete "rm -rf /etc/letsencrypt" will do. Just ensure you installed and use the latest certbot.
     
    Last edited: Sep 1, 2018
  3. SamTzu

    SamTzu Active Member

    That didn't help.
    It's odd. I think there is a bug somewhere because Apache keeps offering the first website name to browser instead of the correct one.
    I have wasted hours on this and can't figure out why Apache can't serve proper site name to browser.
    Apache .conf file and ISPConfig ssl links are all in order.
     
  4. ahrasis

    ahrasis Well-Known Member

    I think you rather have dns problem. Dig the intended domains and servers for answers.
     
  5. SamTzu

    SamTzu Active Member

    LOL :)
    You are correct. Two commands with dig revealed the truth that I actually alluded my self in my first post on this thread. DNS change has not propagated trough yet.
    I can't believe I wasted many hours on this.
    I mostly pipe all my traffic trough my own VPN & DNS servers (to prevent just this kind of stuff) but apparently my Ubuntu 18 LTS DHCP connection had somehow reset to ISP's default DNS. I don't know why it's not honoring the manually defined DNS servers in the network manager.
    That's why it's good to have more than one head in the mix.
     

Share This Page