Token not appearing /.well-known/acme-challenges

[swilsoncarr]

Trying to add SSL to a gitlab server using Let’s Encrypt and Certbot.

I can save a test.txt in the webroot and access it in /.well-known/acme-challenge/

I have changed the setting so /var/www/letsencrypt/ is the root for the token to be accessed.

The settings in the gitlab.rb are:

nginx['custom_gitlab_server_config'] = "location ^~ /.well-known { root /var/www/letsencrypt; }"

The error I am seeing is:

Failed authorization procedure. gitlab.example.co.uk (http-01): urn:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gitlab.example.co.uk/.well-known/acme-challenge/arUuWGLPGjQRw333SPHMzzlNezA1Zitjw4a9BrTFJ7w: Timeout

I have been searching for days not, but no luck.

[schoen]

Could you tell us your real domain? Maybe you have an AAAA record but aren’t answering IPv6 requests?

[swilsoncarr]

gitlab.nllashes.co.uk but its a VM and not accessible outside the network

[schoen]

How is the certificate authority going to validate that you’ve posted the challenge file if it can’t connect to your host from the Internet?

[swilsoncarr]

the domain a record is pointing to the WAN and then points to the correct server we have it working on one of the gitlab installs. Just this one is not having it, I have added the test.txt and can access that.

[schoen]

There’s no publicly-visible A record at all for gitlab.nllashes.co.uk so far—so there’s no way for Let’s Encrypt to confirm that you’re the operator of that site.

[swilsoncarr]

sorry that is the wrong domain gitlab.nlcloud.co.uk

[sahsanu]

I’ve tried to reach gitlab.nlcloud.co.uk from different countries and I only get timeouts. Are you sure your site is reachable from internet?