I run a small webserver with a nextcloud instance.
Before I ran it behind my ISP router and all was well. I used the certbot script to renew the certificates.
Then I switched to Pfsense. All ran fine until the certificate ran out.
When I run the Certbot script I get a warning that I have an issue with my firewall.
Pfsense is set to default, the only thing I changed was the NAT to forward to my webserver on HTTPS and HTTP. (this is working fine).
I am using a no-ip dynamic updated domain. I don't have access to any DNS records.
I tried to generate the certificates on Pfsense itself but that seems to give the same issues.
Any tips on how to troubleshoot this?
Many thanks!
Karel.
My domain is:editoor.ddns.net
I ran this command:
sudo certbot --apache
It produced this output:
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator apache, Installer apache
Starting new HTTPS connection (1): acme-v02.api.letsencrypt.org
Which names would you like to activate HTTPS for?
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
1: editoor.ddns.net
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Select the appropriate numbers separated by commas and/or spaces, or leave input
blank to select all options shown (Enter 'c' to cancel): 1
Cert is due for renewal, auto-renewing...
Renewing an existing certificate for editoor.ddns.net
Performing the following challenges:
http-01 challenge for editoor.ddns.net
Waiting for verification...
Challenge failed for domain editoor.ddns.net
http-01 challenge for editoor.ddns.net
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: editoor.ddns.net
Type: connection
Detail: Fetching
http://editoor.ddns.net/.well-known/acme-challenge/H5u2Y9IINzRysZx1V5PGiXXxDOY99rfFUqdhUcOQT14:
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.
My web server is (include version): Server version: Apache/2.4.6 (CentOS)
Server built: Nov 16 2020 16:18:20
The operating system my web server runs on is (include version): CentOS 7
My hosting provider, if applicable, is: no-ip.
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 1.11.0