The server could not connect to the clien│the exact distribution terms for each program are described in the t 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: campaign.medicastore.com

I ran this command: letsencrypt --installer apache -d campaign.medicastore.com

It produced this output: The server could not connect to the client to verify the domain :: Fetching http://campaign.medicastore.com/.well-known/acme-challenge/OQQma9wkqfKQQqCJ0qHq5ibP6pPEujc5h3PzxaGz0E4: Error getting validation data

My web server is (include version): apache

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

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

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

Weird!

Does that happen reliably, say, if you try once or twice more?

letsencrypt certonly --apache -d campaign.medicastore.com --dry-run

Just adding some research. You should follow @_az’s suggestion.

campaign.medicastore.com appears to be serving the wrong certificate (anaconda.medicastore.com). I just get a 404 Not Found when I visit the link to the challenge file, which is likely expected since it probably was cleaned up already. The point is that there’s no access error.

i try more than 10 times… im already using dry run, but i’ve got some error

Ya, im already research that yesterday, anaconda is one of my subdomain ( in same server ) and using letsencrypt too… IDk why its return 404…