Having issue renewing certificate

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 (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: teu.talentegg.ca

I ran this command: certbot-auto renew --dry-run

It produced this output:
The following certs could not be renewed:
/etc/letsencrypt/live/talentegg.ca/fullchain.pem (failure)
** DRY RUN: simulating ‘certbot renew’ close to cert expiry
** (The test certificates above have not been saved.)


1 renew failure(s), 0 parse failure(s)

IMPORTANT NOTES:

  • The following errors were reported by the server:

    Domain: teu.talentegg.ca
    Type: unauthorized
    Detail: Invalid response from
    http://teu.talentegg.ca/.well-known/acme-challenge/l0NLqafBudVqmsnDPb42JT6vC6KH0jagizAifkB94J4
    [52.18.16.242]: “\r\n502 Bad
    Gateway\r\n<body
    bgcolor=“white”>\r\n

    502 Bad
    Gateway

    \r\n\r”

    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.

Hi @tEgg,

It looks like every HTTP URL on your site gives a 502 Bad Gateway error, except for the homepage. However, this is difficult to notice in a browser because your site also uses the HTTP Strict Transport Security (HSTS) mechanism to tell browsers to always use HTTPS instead of HTTP when connecting to the site.

If you try with something other than a browser, or with a browser that’s never visited this site before, you should be able to see the 502 error on all of the HTTP pages—and you’ll need to figure out why this problem exists in your web server configuration.