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:melochenator.com
It produced this output:
My web server is (include version):nginx
The operating system my web server runs on is (include version):Ubuntu 14.04.5 LTS \n \
My hosting provider, if applicable, is:
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 version of my client is (e.g. output of
certbot --version or
certbot-auto --version if you’re using Certbot):certbot 0.28.0
certbot-auto certonly -a webroot --webroot-path=/var/www/melochenator.com/www/html/ -d melochenator.com -d www.melochenator.com
Requesting to rerun /usr/local/sbin/certbot-auto with root privileges…
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Cert not yet due for renewal
You have an existing certificate that has exactly the same domains or certificate name you requested and isn’t close to expiry.
What would you like to do?
1: Keep the existing certificate for now
2: Renew & replace the cert (limit ~5 per 7 days)
Select the appropriate number [1-2] then [enter] (press ‘c’ to cancel): 2
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for melochenator.com
http-01 challenge for www.melochenator.com
Using the webroot path /var/www/melochenator.com/www/html for all unmatched domains.
Waiting for verification…
Cleaning up challenges
Failed authorization procedure. melochenator.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://melochenator.com/.well-known/acme-challenge/UGy2DC3yZRvkYHx6NZpahpYrvPVhzybQAM3fro0NJsg: Connection refused, www.melochenator.com (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://www.melochenator.com/.well-known/acme-challenge/H6ap8hQ5NUR-LogV-AyIxjOyTQ4h4nE0UBBS58yZh14: 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.