Following the instructions here, I can’t get certbox to register my domain.
My domain is:
greg.party
I ran this command:
sudo certbot --nginx -d greg.party -d www.greg.party
I’ve used variations - sometimes only entering … -d greg.party, -d www.greg.party, changing order …
It produced this output:
greg@joeiii:~$ sudo certbot --nginx -d greg.party -d www.greg.party
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Starting new HTTPS connection (1): acme-v01.api.letsencrypt.org
Obtaining a new certificate
Performing the following challenges:
tls-sni-01 challenge for greg.party
tls-sni-01 challenge for www.greg.party
Cleaning up challenges
Cannot find a VirtualHost matching domain greg.party.
My web server is (include version):
Nginx 1.10.3
The operating system my web server runs on is (include version):
Ubuntu 16.04
My hosting provider, if applicable, is:
Digital Ocean
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):
Partially. Here’s a screencap of my domain configuration on digitalocean.com
I have several letsencrypt.log files. Presumably one for every time I’ve run certbot. Some of them are empty, I can’t even access the folder unless I’m root. $ su won’t work.
Could you also post the nginx configuration file that defines the virtual host for those domain names? Are you using the default structure for nginx configuration on your operating system, or did you change or rewrite the nginx configuration in some way?
I’m using Digital Ocean’s Ubuntu 16.04 One-click Ghost (0.11.1) installation.
I’ve added a new user with root permissions and tried to get this cert working, and that’s about it.
Nope, the problem has to do with your nginx configuration (in terms of the actual configuration file parsing). It’s not a network error, but a configuration parsing error — which could potentially be a problem with Certbot rather than your configuration.