My domain is:parrity.com & next.parrity.com
I ran this command:certbot -d next.parrity.com
It produced this output:
Certbot failed to authenticate some domains (authenticator: nginx). The Certificate Authority reported these problems:
Domain: next.parrity.com
Type: unauthorized
Detail: Invalid response from http://next.parrity.com/.well-known/acme-challenge/Hk8Nf40JC_92ADGg-iEu9T29Y9EBwPzG2r4hLkjpolc [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"
Hint: The Certificate Authority failed to verify the temporary nginx configuration changes made by Certbot. Ensure the listed domains point to th is nginx server and that it is accessible from the internet.
My web server is (include version):Linux
The operating system my web server runs on is (include version):
My hosting provider, if applicable, is: DigitalOcean
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): 1.24.0
Hello everyone, I have the following situation on my hands,
I have several droplets hosted on DigitalOcean with my platform - parrity.com
parrity.com points to an I.P of a doplet that has an ip: 46.101.240.67 & sub-domain caled next.parrity.com
For some reason the certificate on that droplet doesn't want to renew, and also the sub-domain and typing the I.P does not work as it gives 404.
However, opening parrity.com works and loads the working app with the outdated certificate.
I suspect this might be a record issue, but not sure where to start. Please help.