Invalid weryfication addres

Please fill out the fields below so we can help you better.

My domain is:

I ran this command: certbot certonly --manual

It produced this output:

Saving debug log to /var/log/letsencrypt/letsencrypt.log
Please enter in your domain name(s) (comma and/or space separated) (Enter 'c’
to cancel)
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for

NOTE: The IP of this machine will be publicly logged as having requested this
certificate. If you’re running certbot in manual mode on a machine that is not
your server, please ensure you’re okay with that.

Are you OK with your IP being logged?

(Y)es/(N)o: Y

Make sure your web server displays the following content at before continuing:


If you don’t have HTTP server configured, you can run the following
command on the target server (as root):

mkdir -p /tmp/certbot/public_html/.well-known/acme-challenge
cd /tmp/certbot/public_html
printf “%s” 32IEltrV3h7zQSzugINLILC9ZiwqQGE3IfgHyiMZxpA.CqF_NYcaM3QPWtPKqebLLtFdDvYQUfzo1bJ9rssG5c4 > .well-known/acme-challenge/32IEltrV3h7zQSzugINLILC9ZiwqQGE3IfgHyiMZxpA

run only once per server:

$(command -v python2 || command -v python2.7 || command -v python2.6) -c
“import BaseHTTPServer, SimpleHTTPServer;
s = BaseHTTPServer.HTTPServer((’’, 80), SimpleHTTPServer.SimpleHTTPRequestHandler);

Press Enter to Continue
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching Error getting validation data


  • The following errors were reported by the server:

    Type: connection
    Detail: Fetching
    Error getting validation data

    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.

My web server is (include version): apache-2.2.23

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

My hosting provider, if applicable, is: self hosted

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 problem is that when certboot is trying to verify if desired content is available under desired locsation

it looses / after domain name and is unable to verify:/

the loss of “/” is happening in your http to https redirection statement.

Here is another example showing the problem is affecting all http requests:
301 Moved Permanently
Location: [following]
Resolving (… failed: Name or service not known.

can you show the :80 vhost config?

1 Like

Fixed(redirection was missing /) :wink:
Thanks for quick reply, it seems like my browser swapped the correct https link and I was convinced that link is good and only certboot is having problems since i was able to reach the http link correctly with my browser;)

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