Connection refused

My domain is:

I ran this command:
certbot certonly -n -v --debug-challenges --debug --webroot -w /var/www/certbot --staging --email -d --rsa-key-size 4096 --agree-tos

It produced this output:

Challenges loaded. Press continue to submit to CA. Pass "-v" for more info about


  • The following errors were reported by the server:

    Type: connection
    Detail: Fetching
    Connection refused

    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.

  • Your account credentials have been saved in your Certbot
    configuration directory at /etc/letsencrypt. You should make a
    secure backup of this folder now. This configuration directory will
    also contain certificates and private keys obtained by Certbot so
    making regular backups of this folder is ideal.

My web server is (include version):

nginx 1.18.0

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

nginx:stable container image

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):
certbot/certbot:latest container image - v1.8.0

1 Like

Hi @lioramilbaum

there is no answer. Now not a Connection refused, instead, a timeout. See

Domainname Http-Status redirect Sec. G -14 10.030 T
Timeout - The operation has timed out -14 10.030 T
Timeout - The operation has timed out -14 9.997 T
Timeout - The operation has timed out

Only timeouts.

If you want to use webroot, a running webserver is required. Runs the http port 80?


from that machine?

Do you run certbot on that machine?

If yes, it's a router / firewall problem.

1 Like

Thanks for the prompt reply. With your insight, I've managed to solve the problem.


Happy to read that you have found a solution. Thanks reporting back :+1:

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