Errors installing SSL cert. on my second domain, please help!


#1

I get this error whenever I try to install the cert on my second domain. It worked perfectly on my other one. I have no idea why, and any assistance would be most appreciated. I’m using Plesk 12.5, PHP 7.0.9 and Ubunto 14.04. Thanks!

Error: Let's Encrypt SSL certificate installation failed: Failed letsencrypt execution: Failed authorization procedure. avulsion2.com (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Could not connect to http://avulsion2.com/.well-known/acme-challenge/FQhnx4DY98Jh-jp4a3qtfxIP07NDXd_4evGnJNegu1Y
IMPORTANT NOTES:
- The following errors were reported by the server:

Domain: avulsion2.com
Type: connection
Detail: Could not connect to
http://avulsion2.com/.well-known/acme-challenge/FQhnx4DY98Jh-jp4a3qtfxIP07NDXd_4evGnJNegu1Y

To fix these errors, please make sure that your domain name was
entered correctly and the DNS A 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.

#2

There’s nothing responding on the IP address behind that hostname:

osiris@desktop ~ $ ping avulsion2.com
PING avulsion2.com (209.126.98.221) 56(84) bytes of data.
^C
--- avulsion2.com ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9000ms

osiris@desktop ~ $ telnet avulsion2.com 80
Trying 209.126.98.221...
^C
osiris@desktop ~ $ telnet avulsion2.com 443
Trying 209.126.98.221...
^C
osiris@desktop ~ $ 

You sure you’ve got the right IP address associated with that hostname in your DNS settings?


#3

Pretty sure, yes. The site even works for me and I’ve added basic code there. Would the site “work” for me, but no one else? The domain is on GoDaddy and I pointed it to the IP of my server…


#4

Are you on the same LAN as the server? If so there might be a firewall that you’re behind but we’re not.


#5

I just chatted with my registrar. Apparently the domain didn’t fully resolve when I updated the nameservers. They corrected it and suggested I wait about 12 hours and then try again!

I’ll update the thread at that point. Thanks!!


#6

bah, I gave up on it. Besides now I don’t have to renew TWO domains. :slight_smile:


#7

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.