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:
I ran this command:
sudo certbot --authenticator standalone --installer nginx -d gonsernas.zapto.org --pre-hook "service nginx stop" --post-hook "service nginx start"
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator standalone, Installer nginx
Running pre-hook command: service nginx stop
Obtaining a new certificate
Performing the following challenges:
http-01 challenge for gonsernas.zapto.org
Waiting for verification...
Cleaning up challenges
Running post-hook command: service nginx start
Failed authorization procedure. gonsernas.zapto.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://gonsernas.zapto.org/.well-known/acme-challenge/3N6nKsSq-YYNU7Vo0QRBpDkpkOK5Ti7c_OGVee_dANk: Connection refused
The following errors were reported by the server:
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.
My web server is (include version):
The operating system my web server runs on is (include version):
Raspberry Pi 3b
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):
i think no
The version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you're using Certbot):
python-certbot-nginx is already the newest version (0.31.0-1).