@GregorR1 (Gregor R) posted a new topic, subject "Sudo Certbot renew failed". It read:

   My domain is: test.buildingmanagementsystems.uk
    
    I ran this command: sudo certbot renew
    
    It produced this output:
    [code] 
        Saving debug log to /var/log/letsencrypt/letsencrypt.log
        
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Processing /etc/letsencrypt/renewal/test.buildingmanagementsystems.uk.conf
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        Cert is due for renewal, auto-renewing...
        Plugins selected: Authenticator standalone, Installer None
        Renewing an existing certificate
        Performing the following challenges:
        http-01 challenge for test.buildingmanagementsystems.uk  
        Waiting for verification...
        Cleaning up challenges
        Attempting to renew cert (test.buildingmanagementsystems.uk) from 
        /etc/letsencrypt/renewal/test.buildingmanagementsystems.uk.conf produced an unexpected error:  
        Failed authorization procedure. test.buildingmanagementsystems.uk (http-01): 
        urn:ietf:params:acme:error:connection 8b7c:f320:99b9:690f:4595:cd17:293a:c069 The server could not connect to the client to verify the 
        domain 8b7c:f320:99b9:690f:4595:cd17:293a:c069 Fetching http://test.buildingmanagementsystems.uk/.well-known/acme- 
        challenge/UumVU0hF6wdx1mL4cN-S5-MeuszAO1L3FflMW2kiAY8: Timeout during connect (likely 
        firewall problem). Skipping.
        All renewal attempts failed. The following certs could not be renewed:
        /etc/letsencrypt/live/test.buildingmanagementsystems.uk/fullchain.pem (failure)
        
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        
        All renewal attempts failed. The following certs could not be renewed:
        /etc/letsencrypt/live/test.buildingmanagementsystems.uk/fullchain.pem (failure)
        - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
        1 renew failure(s), 0 parse failure(s)
        
        IMPORTANT NOTES:
         - The following errors were reported by the server:
        
           Domain: test.buildingmanagementsystems.uk
           Type:   connection
           Detail: Fetching
           http://test.buildingmanagementsystems.uk/.well-known/acme-challenge/UumVU0hF6wdx1mL4cN- 
        S5-MeuszAO1L3FflMW2kiAY8:
           Timeout during connect (likely firewall problem)
        
        To fix these errors, please make sure that your domain name was
        entered correctly and the DNS A/AAAA record(s) for that domain
        contain(s) the right IP address. Additionally, please check that
        your computer has a publicly routable IP address and that no
        firewalls are preventing the server from communicating with the
        client. If you're using the webroot plugin, you should also verify
        that you are serving files from the webroot path you provided.
        
    [/code]
    
    My web server is (include version): Thingsboard v.3.0.1PE
    
    The operating system my web server runs on is (include version): Ubuntu 18.04.2
    
    My hosting provider, if applicable, is: AWS
    
    I can login to a root shell on my machine (yes or no, or I don't know): Yes
    
    I'm using a control panel to manage my site (no, or provide the name and version of the control panel): no
    
    The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): 0.27.0
    
    I got an email regarding this certificate as it is now invalid. I thought it would automatically renew. But it obviously has not. When I tried to renew it manually I received the error above.
    
    Hopefully someone will be able to shine some light on this issue as this is the first time I've set something like this up.
    
    Thanks,  
    Gregor
      *[ACME]: Automated Certificate Management Environment

After which, @Osiris added

    Is port 80 open in **all** your firewalls?
      *[ACME]: Automated Certificate Management Environment

After which, @GregorR1 (Gregor R) added

    Hi, I checked my AWS Security group and it only had HTTPS:443 open. I added I've HTTP:80 and re-ran the command and it has now successfully renewed the certificate. Will this be why it did not auto renew?
    
    Thanks,  
    Gregor
      *[ACME]: Automated Certificate Management Environment

Then @Osiris said

    GregorR1:
    
    > Will this be why it did not auto renew?
    
    Could be. Could also be there wasn't a cronjob or systemd timer installed. Normally, cron would e-mail you any errors. I have no idea how systemd handles errors.
      *[ACME]: Automated Certificate Management Environment

So @system (system) replied

    This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
      *[ACME]: Automated Certificate Management Environment


{'source': 'discourse', 'url': 'https://community.letsencrypt.org/t/sudo-certbot-renew-failed/128938', 'title': 'Sudo Certbot renew failed', 'views': 489, 'has_accepted_answer': False, 'word_count': 567, 'like_count': 6, 'reply_count': 1, 'participant_count': 2, 'posts': 5, 'tags': '', 'author': '@GregorR1 (Gregor R)', 'participants': '@GregorR1 (Gregor R), @Osiris, @system (system)', 'image_url': [None], 'created_at': '2020-07-20T13:53:45.273Z', 'last_posted_at': '2020-08-19T16:25:31.869Z'}