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: http://cloud-sanford.dyndns.org
I ran this command:
sudo certbot-auto renew --webroot -w /var/www/nextcloud
It produced this output:
root@nextcloud:/var/www/nextcloud# sudo certbot-auto renew --webroot -w /var/www/nextcloud
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Cert is due for renewal, auto-renewing…
Plugins selected: Authenticator webroot, Installer None
Running pre-hook command: service apache2 stop
Renewing an existing certificate
Performing the following challenges:
http-01 challenge for cloud-sanford.dyndns.org
Using the webroot path /var/www/nextcloud for all unmatched domains.
Waiting for verification…
Challenge failed for domain cloud-sanford.dyndns.org
http-01 challenge for cloud-sanford.dyndns.org
Cleaning up challenges
Attempting to renew cert (cloud-sanford.dyndns.org) from /etc/letsencrypt/renewal/cloud-sanford.dyndns.org.conf produced an unexpected error: Some challenges have failed… Skipping.
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud-sanford.dyndns.org/fullchain.pem (failure)
All renewal attempts failed. The following certs could not be renewed:
/etc/letsencrypt/live/cloud-sanford.dyndns.org/fullchain.pem (failure)
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):
apache2
The operating system my web server runs on is (include version):
Ubuntu 18.04.1 LTS
My hosting provider, if applicable, is:
dyndns
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.31.0
certbot 0.34.2
Dear juergen,
Thank you, As you explained, my https was redirected to https and I was trying to renew certificates through 443, but its got failed.
I tried different methods and stopping http redirection for checking .well-known/acme-challenge/1234 file access, its got access from url but o curl its shows permanently redirect 301
so i hope the same issue stopping certificate renewal, please advice
I don't see a redirect http -> https. I see a http timeout.
So http-01 validation can't work.
A correct redirect http -> https isn't a problem that stops certificate renewal. Letsencrypt follows these redirects. But the first check goes to port 80, there must be an answer.
I did the above method though sudo certbot run -a webroot -i apache -w /var/www/nextcloud -d cloud-sanford.dyndns.org
You can use dns-01 validation and --manual