Upgrade LetsEncrypt properly

Discussion in 'Installation/Configuration' started by labsy, Feb 13, 2018.

  1. labsy

    labsy Member

    Hi,
    On my older ISPConfig server I have LetsEncrypt setup with a lot of pain. I have been trying different methods, until finally I got it working. Ind since I don't touch it.
    Now I found upgrade warning in /var/logs/letsencrypt/letsencrypt.log :
    Code:
    2018-02-13 06:14:01,841:DEBUG:certbot.main:certbot version: 0.21.1
    2018-02-13 06:14:01,841:DEBUG:certbot.main:Arguments: ['-n', '--text', '--agree-tos', '--expand', '--authenticator', 'webroot', '--server', 'https://acme-v01.api.letsencrypt.org/directory', '--rsa-key-size', '4096', '--email........', '/usr/local/ispconfig/interface/acme']
    2018-02-13 06:14:01,841:DEBUG:certbot.main:Discovered plugins: PluginsRegistry(PluginEntryPoint#apache,PluginEntryPoint#manual,PluginEntryPoint#nginx,PluginEntryPoint#null,PluginEntryPoint#standalone,PluginEntryPoint#webroot)
    2018-02-13 06:14:01,848:WARNING:certbot.cli:You are running with an old copy of letsencrypt-auto that does not receive updates, and is less reliable than more recent versions. We recommend upgrading to the latest certbot-auto script, or using native OS packages.
    2018-02-13 06:14:01,849:DEBUG:certbot.cli:Deprecation warning circumstances: /root/.local/share/letsencrypt/bin/letsencrypt / {'LANG': 'en_US.UTF-8', 'SHELL': '/bin/sh', 'SHLVL': '3', 'PWD': '/usr/local/ispconfig/server', 'LOGNAME': 'root', 'HOME': '/root', 'PATH': '/sbin:/usr/sbin:/bin:/usr/bin:/usr/local/sbin:/usr/local/bin:/usr/X11R6/bin', '_': '/root/.local/share/letsencrypt/bin/letsencrypt'}
    
    Can somebody please point me into right method of upgrading this one? Which method to use?
    ....or just update ISPConfig and it will do magic behind the scenes?
    ...or even just pat-get update ?
    BTW...OS is Ubuntu 12.04.5 LTS
     
  2. till

    till Super Moderator Staff Member ISPConfig Developer

    ISPConfig is not related to Certbot. The way you update depends on the way you used to install certbot. If you installed it with apt, then update it with apt. If you installed it from source, then install the new version from source as well. I used several methods to install certbot on my servers, some with apt, some from source, and I never had any issues with installing it. But I must admit that I don't have any server with an OS old as Ubuntu 12.04, so there might be issues in installing Certbot on that old version. For ISPConfig, it does not matter how you installed certbot.
     
  3. labsy

    labsy Member

    Hi Till,
    interesting...in fact I do not remember which method I used when finally got it working, so I am lost now when I do not know how to upgrade. I remember being here on forum said many times, that one should not use this method, but rather that method, where I do not know which is which and which one I used :)
    Any idea, how should I determine which method I used to install?
     
  4. Jesse Norell

    Jesse Norell Well-Known Member

    at a command prompt run 'which certbot'to see where it is installed; if it is a system directory like /usr/bin/ it likely was from a package; if in /opt or /root or similar, it was likely from source.

    Offhand, can you even get a certbot .deb for Ubuntu 12?
     
  5. ahrasis

    ahrasis Active Member

    I would suggest you upgrade to 16.04 LTS since 12.04 LTS is no longer supported and by May, 18.04 LTS will be ready.
     
  6. Poliman

    Poliman Member

    I use 16.04 LTS and I suppose I would try update to 18.04 but is there any tutorial how to do this for server with running ISP? I did move one time for server without ISP - copy all databases, needed files, normally upgrade system from console then - using rsync - move all data to their proper places. That server was for testing purposes and it had not ISP.
     
  7. ahrasis

    ahrasis Active Member

    @Poliman, you may want to follow what @Jesse Norell already suggested in other thread. I took almost similar steps when upgrading mine. I quote:
     
  8. Poliman

    Poliman Member

    Hmm, so it would be like:
    1. Copy required data.
    2. Do upgrade or fresh install of OS.
    3. Install ISP from Perfect Server tutorial.
    4. Move data from backup place to their proper locations.

    These steps above are quite general. ;)
     
  9. labsy

    labsy Member

    Hjah...
    Code:
    # which certbot
    You have new mail in /var/mail/root
    But I found certbot in /opt/eff.org/certbot/venv/
     
  10. labsy

    labsy Member

    Regarding upgrade...I have very bad experinece with upgrades. I guess all customizations, like LE SSLs for ISPConfig, phpMyAdmin will be gone. Also Apache has different configs from 2.2 further, so my customizations will be gone.
    So I have a habit to simply deploy new server, new install and put new hosting customers there. Also to older customers I offer "free" package on new server, which they accept like I would give them something for free and they like me :)
     
  11. ahrasis

    ahrasis Active Member

    That is a very smart move.
     

Share This Page