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. crt.sh | 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: hhpncpi.duckdns.org
i am using nextcloud installed on raspberry pi 4. wanted to create ssl cert for NC. when i entered domain name, email address and hit apply to create letsencrypt certificate i ran into below error everytime. pls note i have disabled firewall from both router as well in pc installed internet security. pls assist.
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 hhpncpi.duckdns.org
Using the webroot path /var/www/nextcloud for all unmatched domains.
Waiting for verification...
Cleaning up challenges
Failed authorization procedure. hhpncpi.duckdns.org (http-01): urn:ietf:params:acme:error:connection :: The server could not connect to the client to verify the domain :: Fetching http://hhpncpi.duckdns.org/.well-known/acme-challenge/xNASvNQoMzgbRlHNZjB3oGBS1xg5S284j-hfAhSwj8A: Timeout during connect (likely firewall problem)
IMPORTANT NOTES:
- The following errors were reported by the server:
Domain: hhpncpi.duckdns.org
Type: connection
Detail: Fetching
http://hhpncpi.duckdns.org/.well-known/acme-challenge/xNASvNQoMzgbRlHNZjB3oGBS1xg5S284j-hfAhSwj8A:
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.