I’m using nextcloudpi hosted on a Raspberry pi at home. I am not an experienced user, so please, bear with me. My server was running smoothly until the certificate was not renewed, it was concomitant to a nextcloudpi update that did not succeed. The update problem is now fixed, but I can’t renew my certificate. I think it may be not related with the update anymore, as I had this same problem about 2 years ago which resolved by itself few months later. But it is quite annoying to have this issue and not knowing how to deal with it. I believe it’s related to IPv6, but I have zero knowledge on that.
My domain is: vercingeto.freeboxos.fr
I ran this command: Running letsencrypt from the TUI of nextcloupi leads to:
Running letsencrypt Saving debug log to /var/log/letsencrypt/letsencrypt.log Plugins selected: Authenticator webroot, Installer None Obtaining a new certificate Performing the following challenges: http-01 challenge for vercingeto.freeboxos.fr Using the webroot path /var/www/nextcloud for all unmatched domains. Waiting for verification... Cleaning up challenges Failed authorization procedure. vercingeto.freeboxos.fr (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching https://vercingeto.freeboxos.fr/.well-known/acme-challenge/kQGybT3-8Do6Lpz2ERf8MOz6MUfhGs7V79awHy7Bvhs: Timeout during connect (likely firewall problem) IMPORTANT NOTES: - The following errors were reported by the server: Domain: vercingeto.freeboxos.fr Type: connection Detail: Fetching https://vercingeto.freeboxos.fr/.well-known/acme-challenge/kQGybT3-8Do6Lpz2ERf8MOz6MUfhGs7V79awHy7Bvhs: 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.
Here is the letsdebug output: https://letsdebug.net/vercingeto.freeboxos.fr/30867
Here are the info of the server:
NextCloudPi version v1.10.7 NextCloudPi image NextCloudPi_10-05-18 distribution Raspbian GNU/Linux 9 \n \l automount yes USB devices sda datadir /media/USBdrive/ncdata data in SD no data filesystem btrfs data disk usage 730G/932G rootfs usage 2.4G/15G swapfile /var/swap dbdir /var/lib/mysql Nextcloud check ok Nextcloud version 220.127.116.11 HTTPD service up PHP service up MariaDB service up Redis service up Postfix service up internet check ok port check 80 open port check 443 open interface eth0 certificates vercingeto.freeboxos.fr NAT loopback yes uptime 23:05
My hosting provider, if applicable, is: NA
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 0.28.0 (not sure if nextcloudpi is using the same)
What should I do ?