Hi all,
I'm kind of stuck getting the certificate from letsencrypt to renew on my nextcloud (official plugin) install.
I'm using the certbot webroot method to do so. The command I'm using (to test) :
After which I choose the webroot option and input the webroot of my nextcloud install : /usr/local/www/nextcloud
The error I get from certbot is the following :
Thing is, I can access the webroot from a web browser without any issue. To double check this, I started the certbot script with the above command, but stopped its execution before it could arrive at timeout. Checking on the command line, there was indeed a challenge file that had appeared at :
So I just pointed my web browser at the url :
...and it did serve me the file, I was able to download it.
So why does the letsencrypt CA server have trouble fetching the challenge from my nextcloud server ? Does anyone have any clues to possible explanations ?
All the best,
Guillaume
I'm kind of stuck getting the certificate from letsencrypt to renew on my nextcloud (official plugin) install.
I'm using the certbot webroot method to do so. The command I'm using (to test) :
Code:
certbot certonly -d mydomain
After which I choose the webroot option and input the webroot of my nextcloud install : /usr/local/www/nextcloud
The error I get from certbot is the following :
Code:
Domain: cloud.mydomain.com Type: connection Detail: Fetching http://cloud.mydomain.com/.well-known/acme-challenge/Mj1vxrbQl1J6UVxGQGwYeIUh3Q_eO0EPrTitZqL-Lxs: Timeout during connect (likely firewall problem) 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.
Thing is, I can access the webroot from a web browser without any issue. To double check this, I started the certbot script with the above command, but stopped its execution before it could arrive at timeout. Checking on the command line, there was indeed a challenge file that had appeared at :
Code:
/usr/local/www/nextcloud/.well-known/acme-challenge/Mj1vxrbQl1J6UVxGQGwYeIUh3Q_eO0EPrTitZqL-Lxs
So I just pointed my web browser at the url :
Code:
cloud.mydomain.com/.well-known/acme-challenge/Mj1vxrbQl1J6UVxGQGwYeIUh3Q_eO0EPrTitZqL-Lxs
...and it did serve me the file, I was able to download it.
So why does the letsencrypt CA server have trouble fetching the challenge from my nextcloud server ? Does anyone have any clues to possible explanations ?
All the best,
Guillaume