The server could not connect to the client to verify the domain

Please fill out the fields below so we can help you better. Note: you must provide your domain name to get help. Domain names for issued certificates are all made public in Certificate Transparency logs (e.g. https://crt.sh/?q=example.com), so withholding your domain name here does not increase secrecy, but only makes it harder for us to provide help.

My domain is: socialpops.co.uk

I ran this command: certbot --apache --staging

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache

Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: socialpops.co.uk
2: www.socialpops.co.uk
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel):
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for socialpops.co.uk
http-01 challenge for www.socialpops.co.uk
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. www.socialpops.co.uk (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://socialpops.co.uk/.well-known/acme-challenge/FDDhneXRpuC_SK3nkwc-_U5xi5BJCpQPNo1CfNzKJMc: Error getting validation data

IMPORTANT NOTES:
 - The following errors were reported by the server:

   Domain: www.socialpops.co.uk
   Type:   connection
   Detail: Fetching
   https://socialpops.co.uk/.well-known/acme-challenge/FDDhneXRpuC_SK3nkwc-_U5xi5BJCpQPNo1CfNzKJMc:
   Error getting validation data

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

My web server is (include version): Bytemark VPS

The operating system my web server runs on is (include version): Debian 9

My hosting provider, if applicable, is:

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): no

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you’re using Certbot): certbot 0.28.0

I’ve been trying to get an SSL on this domain and have been getting the response listed above. The DNS is configured correctly. I’ve also tried the manual version and created the challenges myself and I got the same error. It seems odd to me that it is looking to hit https://socialpops.co.uk/.well-known/acme-challenge/FDDhneXRpuC_SK3nkwc-_U5xi5BJCpQPNo1CfNzKJMc even though the site doesn’t have an SSL yet.

Any help would be much appreciated!

Hi @angus-purr

your SSL isn’t configured ( https://check-your-website.server-daten.de/?q=socialpops.co.uk ).

Result: Your server sends http content over port 443. That isn’t a problem if you don’t have redirects http -> https. But you have redirects, so it’s impossible that Letsencrypt finds the correct file:

Domainname Http-Status redirect Sec. G
http://www.socialpops.co.uk/
46.43.15.182 301 https://www.socialpops.co.uk/ 0.080 A
http://socialpops.co.uk/
46.43.0.74 200 0.093 H
https://www.socialpops.co.uk/
46.43.15.182 301 https://socialpops.co.uk/ 0.726 A
https://socialpops.co.uk/
46.43.0.74 -4 0.136 W
SendFailure - The underlying connection was closed: An unexpected error occurred on a send. The handshake failed due to an unexpected packet format.

Same with your /.well-known/acme-challenge subdirectory.

So:

  • Fix your SSL (perhaps use a self signed certificate) (or)
  • remove the redirects http -> https, recheck your domain, if that works. Then try it again.

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