I’m obfuscating the domain name here because while publicly accessible, this multi-domain server hosts only testing environments for a web application, and I do not wish to have it listed on the internet.
My domain is: example.com
I ran this command:
certbot certonly --test-cert --webroot -d machine1.example.com -d env01.example.com -d env02.example.com
And it worked fine.
Then, I ran the exact same command, without the
certbot certonly --webroot -d machine1.example.com -d env01.example.com -d env02.example.com
And it failed.
It produced this output:
Failed authorization procedure. env01.example.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Could not connect to env01.example.com IMPORTANT NOTES: - The following errors were reported by the server: Domain: env01.example.com Type: connection Detail: Could not connect to env01.example.com
My operating system is (include version):
Debian 8 Jessie (
Linux machine1 3.16.0-4-amd64 #1 SMP Debian 3.16.39-1 (2016-12-30) x86_64 GNU/Linux)
My web server is (include version): Nginx version:
My hosting provider, if applicable, is:
I can login to a root shell on my machine: yes
I’m using a control panel to manage my site (no, or provide the name and version of the control panel): DNS is managed through Godaddy’s web interface.
What I don’t get is why the hell is everything working fine when using staging environment, and some domain fail to validate when trying to generate production certificates.
Every subdomain I provide to
certbot for validation has its own web root, and is publicly accessible.
I don’t get what’s going wrong.
Any help appreciated!