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=ottawakaraoke.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.
My domain is:
I ran this command:
sudo certbot --apache
It produced this output:
Which names would you like to activate HTTPS for?
My web server is (include version):
The operating system my web server runs on is (include version):
debian 8 jessie
My hosting provider, if applicable, is:
I can login to a root shell on my machine (yes or no, or I don’t know):
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):
latest version of certbot
I changed my ip address and am using a new host
i receive the following error
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.
I have a new ip address, how what is the next step?
Update your DNS records. If you’ve already done that, post the rest of the error message you got.
I have already posted the error message.
I’m using that command to renew the certificate.
No, you’ve posted what certbot suggests you check to resolve the error–the error message is the part before “to fix these errors”.
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for canadakaraoke.com
http-01 challenge for karaokeottawa.com
http-01 challenge for ottawakaraoke.ca
http-01 challenge for ottawakaraoke.com
http-01 challenge for sing.ottawakaraoke.com
http-01 challenge for www.canadakaraoke.com
http-01 challenge for www.karaokeottawa.com
http-01 challenge for www.ottawakaraoke.ca
http-01 challenge for www.ottawakaraoke.com
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. canadakaraoke.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://canadakaraoke.com/.well-known/acme-challenge/LbP2XA0raIyvFN6EJ280LPC5ul0AUma_YY75nBttEMU: Error getting validation data
OK, this is the problem–the Let’s Encrypt servers can’t connect to your server at all. Is your new IP address 22.214.171.124? Because that’s what a DNS query is returning:
dan@Dan-MacBook-Pro-2453 ~ host canadakaraoke.com
canadakaraoke.com has address 126.96.36.199
dan@Dan-MacBook-Pro-2453 ~ host karaokeottawa.com
karaokeottawa.com has address 188.8.131.52
dan@Dan-MacBook-Pro-2453 ~ host ottawakaraoke.ca
ottawakaraoke.ca has address 184.108.40.206
dan@Dan-MacBook-Pro-2453 ~ host ottawakaraoke.com
ottawakaraoke.com has address 220.127.116.11
If it isn’t, as I suggested earlier, update your DNS records. If that’s correct, make sure Apache is running on port 80 and that you don’t have a firewall blocking anything on that port.
Yes, that is the new IP address of the server
But Windows Defender doesn’t LIKE your site:
@rg305 try again now…
it should be scanning correctly
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.