# Certificate renewal failure **URL:** \ **Category:** Help\ **Created:** [October 17, 2020, 4:59pm UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256 "2020-10-17T16:59:35Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Mobin\_Philip](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Mobin\_Philip](https://community.letsencrypt.org/u/Mobin_Philip)\ **Post date:** [October 17, 2020, 4:59pm UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256/1 "2020-10-17T16:59:35Z")
My domain is: test-api.pickleapp.in I ran this command: sudo certbot renew --force-renewal It produced this output: Attempting to renew cert (test-api.pickleapp.in) from /etc/letsencrypt/renewal/test-api.pickleapp.in.conf produced an unexpected error: Failed authorization procedure. test-api.pickleapp.in (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching [http://test-api.pickleapp.in/.well-known/acme-challenge/qrme6LuG-af0V9JS3DjRTUP-UYpo5nkMjY1RCEn7A4U:](http://test-api.pickleapp.in/.well-known/acme-challenge/qrme6LuG-af0V9JS3DjRTUP-UYpo5nkMjY1RCEn7A4U:) Timeout during connect (likely firewall problem). Skipping. All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/test-api.pickleapp.in/fullchain.pem (failure) * * * All renewal attempts failed. The following certs could not be renewed: /etc/letsencrypt/live/test-api.pickleapp.in/fullchain.pem (failure) * * * 1 renew failure(s), 0 parse failure(s) IMPORTANT NOTES: - The following errors were reported by the server: The operating system my web server runs on is (include version):ubuntu My hosting provider, if applicable, is: I can login to a root shell on my machine (yes or no, or I don't know): yes The version of my client is (e.g. output of `certbot --version` or `certbot-auto --version` if you're using Certbot): ---
**Author:** ![griffin](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/griffin/32/50204_2.png) [@griffin](https://community.letsencrypt.org/u/griffin)\ **Post date:** [October 17, 2020, 5:20pm UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256/2 "2020-10-17T17:20:16Z")
Welcome to the Let's Encrypt Community, Mobin 🙂 Do you have a firewall in the way? ![Screenshot_20201017-111909_Samsung Internet](https://global.discourse-cdn.com/letsencrypt/original/3X/b/5/b51fe99d7523d519e8f78e85e1b79aae0ed35669.jpeg) ---
**Author:** ![Mobin\_Philip](https://avatars.discourse-cdn.com/v4/letter/m/b5e925/32.png) [@Mobin\_Philip](https://community.letsencrypt.org/u/Mobin_Philip)\ **Post date:** [October 17, 2020, 5:24pm UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256/3 "2020-10-17T17:24:34Z")
We are currently using an AWS EC2, but rather than a normal security group, we don't have a firewall. ---
**Author:** ![rg305](https://sea3.discourse-cdn.com/letsencrypt/user_avatar/community.letsencrypt.org/rg305/32/91314_2.png) [@rg305](https://community.letsencrypt.org/u/rg305)\ **Post date:** [October 18, 2020, 1:26am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256/4 "2020-10-18T01:26:04Z")
I can't reach [http://test-api.pickleapp.in/](http://test-api.pickleapp.in/) either. You will need to get that working before `certbot` can work. Unless you are planning to always use `certbot` in `--standalone` mode. [&2\* readers: Get involved; Be heard. It starts with: **if you read something you like, then like it ❤**] ---
**Author:** ![system](https://global.discourse-cdn.com/letsencrypt/original/3X/c/a/ca6c06ea1ea201324bba7048c6841ce60236468d.png) [@system](https://community.letsencrypt.org/u/system)\ **Post date:** [November 17, 2020, 1:26am UTC](https://community.letsencrypt.org/t/certificate-renewal-failure/136256/5 "2020-11-17T01:26:05Z")
Closed on November 17, 2020, 1:26am UTC This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.