Question

Let's Encrypt Certificate Update Issue

Hi, I’m getting this error when updating our certificate at parrity.com

Domain: parrity.com Type: unauthorized Detail: Invalid response from https://parrity.com/.well-known/acme-challenge/YGTIOs7qXPpAqw_mtMZuXjKdgZvyipwDNvQbK6vKk8Q [46.101.240.67]: “<html>\r\n<head><title>404 Not Found</title></head>\r\n<body>\r\n<center><h1>404 Not Found</h1></center>\r\n<hr><center>nginx/1.19.10</c”

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.

I checked our domain A records, and they do point to the I.P 46.101.240.67, a staging domain - next.parrity.com, which is not part of the certificate and is not active atm { 404 error }.

Could this be the issue?

I just changed the records to the original I.P hoping to fix the issue.

Unfortunately, my co-founder CTO is based in Ukraine and I need to fix this on my own. Idk why they point to the staging server. I’m guessing it could be connected to our automated GitLab CD/CI

Thanks in advance.

Submit an answer


This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Bobby Iliev
Site Moderator
Site Moderator badge
• July 5, 2022

Hi there,

Indeed, in order for Let’s Encrypt to validate your domain name, your A record needs to be pointing to the server IP address that you are running the certbot command on.

As far as I can see from the output you are trying to issue a new certificate for the main domain itself, this means that you need to make sure that the A record of the domain is actually pointing to the correct IP address. Or alternatively, you need to make sure that you run the certbot command on the correct server.

Let me know if you have any questions.

Best,

Bobby

Try DigitalOcean for free

Click below to sign up and get $200 of credit to try our products over 60 days!

Sign up