Certificate renwal issue

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (https://gamify.arrkgroup.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: gamify.arrkgroup.com/

I ran this command: sh /usr/local/bin/renewcert.sh
Notifying user: The following certificates are not due for renewal yet:
The following certificates are not due for renewal yet:
Notifying user: /etc/letsencrypt/live/khushi.arrkgroup.com/fullchain.pem expires on 2024-05-02 (skipped)
/etc/letsencrypt/live/khushi.arrkgroup.com/fullchain.pem expires on 2024-05-02 (skipped)
All renewals failed. The following certificates could not be renewed:
/etc/letsencrypt/live/gamify.arrkgroup.com/fullchain.pem (failure)
/etc/letsencrypt/live/gamifyapi.arrkgroup.com/fullchain.pem (failure)
Notifying user: - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -


Exiting abnormally:
Traceback (most recent call last):
File "/usr/bin/certbot", line 9, in
load_entry_point('certbot==1.11.0', 'console_scripts', 'certbot')()
File "/usr/lib/python2.7/site-packages/certbot/main.py", line 15, in main
return internal_main.main(cli_args)
File "/usr/lib/python2.7/site-packages/certbot/_internal/main.py", line 1421, in main
return config.func(config, plugins)
File "/usr/lib/python2.7/site-packages/certbot/_internal/main.py", line 1318, in renew
renewal.handle_renewal_request(config)
File "/usr/lib/python2.7/site-packages/certbot/_internal/renewal.py", line 497, in handle_renewal_request
len(renew_failures), len(parse_failures)))
Error: 2 renew failure(s), 0 parse failure(s)
2 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: gamify.arrkgroup.com
    Type: connection
    Detail: 59.163.23.110: Fetching
    http://gamify.arrkgroup.com/.well-known/acme-challenge/aNVIiAEL4aBkvOtBQcFdcLJjDslD5aDwa8e5uKQzl6Y:
    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.

  • The following errors were reported by the server:

    Domain: gamifyapi.arrkgroup.com
    Type: connection
    Detail: 59.163.23.110: Fetching
    http://gamifyapi.arrkgroup.com/.well-known/acme-challenge/A4DUqqR0odADHuz5kNS6tGv1iTFpQigINXx-b1iS1H0:
    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.

My web server is (include version):

The operating system my web server runs on is (include version): Cent os 7

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

I'm using a control panel to manage my site (no, or provide the name and version of the control panel):

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot):

Have you closed port 80 since you originally got that cert?

Because the HTTP request from the Let's Encrypt server is not able to reach your server.

The Let's Debug test site is helpful to test as you make changes to restore HTTP access. You must have had it working when you originally got your cert. Check any network config and check the IP address is still correct.

3 Likes

I see the same results as Let's Debug got for @MikeMcQ

$ nmap -Pn -p80,443 gamify.arrkgroup.com
Starting Nmap 7.80 ( https://nmap.org ) at 2024-03-08 23:38 UTC
Nmap scan report for gamify.arrkgroup.com (59.163.23.110)
Host is up.
rDNS record for 59.163.23.110: 59.163.23.110.static.vsnl.net.in

PORT    STATE    SERVICE
80/tcp  filtered http
443/tcp filtered https

Nmap done: 1 IP address (1 host up) scanned in 3.99 seconds
2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.