My domain is: example.com (my domain is not published)
I ran this command:
sudo certbot certonly --manual --preferred-challenges dns -d "*.example.com"
It produced this output:
Successfully received certificate.
My web server is (include version):
nginx version: nginx/1.14.1
The operating system my web server runs on is (include version):
VERSION="8.7 (Stone Smilodon)"
ID_LIKE="rhel centos fedora"
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):
no control panel...SSH
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
I got a
certificate for the
DNS-01 Challenge using the
*.example.com format, and everything went well with that. This is the behaviour:
https://www.example.com # works https://example.com # doesn't work http://example.com # doesn't work example.com # doesn't work www.example.com # doesn't work
As by the error code
NET::ERR_CERT_COMMON_NAME_INVALID, the attempts that aren't working aren't getting to the
nginx.conf directives for a redirect from
port 80 to
port 443. As seen in the first attempt,
port 443 works.
Should I redo the certs using this structure for
sudo certbot certonly --manual --preferred-challenges dns -d "example.com"