I’ve been following the tutorial for SSL certification (https://www.digitalocean.com/community/tutorials/how-to-secure-nginx-with-let-s-encrypt-on-ubuntu-20-04)
overall I am trying to set up a WordPress site on a virtualbox following this tutorial: https://www.digitalocean.com/community/tutorials/how-to-install-linux-nginx-mysql-php-lemp-stack-on-ubuntu-20-04
and I’ve run into a roadblock.
For reference, my domain is ryandick.ca
When running the command:
sudo certbot --nginx -d example.com -d www.example.com
I get the error:
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for ryandick.ca
http-01 challenge for www.ryandick.ca
Waiting for verification...
Challenge failed for domain ryandick.ca
Challenge failed for domain www.ryandick.ca
http-01 challenge for ryandick.ca
http-01 challenge for www.ryandick.ca
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: ryandick.ca
Type: dns
Detail: No valid IP addresses found for ryandick.ca
Domain: www.ryandick.ca
Type: dns
Detail: No valid IP addresses found for www.ryandick.ca
- Your account credentials have been saved in your Certbot
configuration directory at /etc/letsencrypt. You should make a
secure backup of this folder now. This configuration directory will
also contain certificates and private keys obtained by Certbot so
making regular backups of this folder is ideal.
My domain is registered on NameCheap with A Records for www.ryandick.ca and ryandick.ca
The records can be confirmed at https://check-your-website.server-daten.de/?q=ryandick.ca which shows that the a records for both can be found.
I’m quite new to this and not sure how to progress, any info would be appreciated.
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!
Hi there,
In order for Certbot to be able to issue a certificate for your domain name, you need to set your domain name’s A record to the public IP address of the Droplet.
At the moment your A record for the domain name is pointing to t private IP (10.0.2.15) so Let’s encrypt is not able to verify the domain name.
Once you point your domain name to the public IP, you need to run the command again and it should work as expected.
Regards, Bobby
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Get started for free
Sign up and get $200 in credit for your first 60 days with DigitalOcean.*
*This promotional offer applies to new accounts only.