Acme::Client::Error::Timeout

[bsde1234]

When I issue GITLAB_TOKEN="F9H5dZ_eKkYUpdDv" bundle exec jekyll letsencrypt I got like below

Configuration file: /mnt/c/Users/name/Desktop/php-projects/web/tuition/_config.yml
Registering [email protected] to https://acme-v01.api.letsencrypt.org/...
Pushing file to Gitlab
Commiting challenge file as letsencrypt.html
Done Commiting! Check https://gitlab.com/bpmottathai/tuition/commits/master
Going to check http:https://tuition.in/.well-known/acme-challenge/CKWt_6YnAs9NiX2hZT8vHgVC9qtyCUFLG0pQ/ for the challenge to be present...
Waiting 120 seconds before we start checking for challenge..
Got response code 200, file is present!
Requesting verification...
jekyll 3.4.0 | Error:  Acme::Client::Error::Timeout

gitlab-letsencrypt:
  # Gitlab settings

  gitlab_repo:           'bpmottathai/tuition' # Namespaced repository identifier

  # Domain settings
  email:                 '[email protected]'     # Let's Encrypt email address
  domain:                'tuition.in'             # Domain that the cert will be issued for

  # Jekyll settings
  base_path:  './'               # Where you want the file to go
  pretty_url: true              # Add a "/" on the end of the URL... set to `true` if you use permalink_style- pretty
  filename:   'letsencrypt.html' # What to call the generated challenge file

  # Delay settings
  initial_delay: 120 # How long to wait for Gitlab CI to push your changes before it starts checking
  delay_time:     15 # How long to wait between each check once it starts looking for the file

  # Optional settings you probably don't need
  # endpoint  'https://somewhere' # if you're doing the ACME thing outside of letsencrypt
  branch:    'master'            # Defaults to master, but you can use a different branch
  layout:    'null'              # Layout to use for challenge file - defaults to null, but you can change if needed
  scheme:    'http'             # Scheme to use for challenge request; default http

group :jekyll_plugins do
  gem 'jekyll-gitlab-letsencrypt', '0.4.1'
end

Ps: Domain name is representative...

[JustinAiken]

Acme::Client::Error::Timeout is (usually) a transitory hiccup on letsencrypt end... if you rerun at a different time to you get the same error?

It's finding your well-known challenge okay, so gitlab is publishing it live, and the plugin is reading it okay; it's just failing to tell letsencrypt about it..

[japorized]

I'm getting the same problem. I've did this at 2 different dates and this has happened on both days.

[pouyamn]

I am getting it most of the times too, just after a few restarts of docker container it works. Is there any way to increase the wait time to eliminate this error?

[JustinAiken]

From a few days ago it won't just timeout - it won't work anymore, since ACME's v1 API is disabled. So no use tweaking the timeout... See #28