Help: Timeout during connect (likely firewall problem)

Help
1

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: cloud.nikology.dev

I ran this command: Used ncp config tool

It produced this output:

[ letsencrypt ] (Sun 27 Aug 23:01:22 BST 2023)
Saving debug log to /var/log/letsencrypt/letsencrypt.log
Plugins selected: Authenticator webroot, Installer None
Requesting a certificate for cloud.nikology.dev
Performing the following challenges:
http-01 challenge for cloud.nikology.dev
Using the webroot path /var/www/nextcloud for all unmatched domains.
Waiting for verification...
Challenge failed for domain cloud.nikology.dev
http-01 challenge for cloud.nikology.dev
Cleaning up challenges
Some challenges have failed.
IMPORTANT NOTES:

  • The following errors were reported by the server:

Domain: cloud.nikology.dev
Type: connection

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):

The operating system my web server runs on is (include version): nextcloudpi

My hosting provider, if applicable, is: N/A

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): NextcloudPi v1.52.4

The version of my client is (e.g. output of certbot --version or certbot-auto --version if you're using Certbot): certbot v1.12.0

P.S. Kindof new to this stuff.

2

Hello @Nikology, welcome to the Let's Encrypt community. :slightly_smiling_face:

Using the online tool Let's Debug yields these results https://letsdebug.net/cloud.nikology.dev/1593746

ReservedAddress
Fatal
A private, inaccessible, IANA/IETF-reserved IP address was found for cloud.nikology.dev. Let's Encrypt will always fail HTTP validation for any domain that is pointing to an address that is not routable on the internet. You should either remove this address and replace it with a public one or use the DNS validation method instead.
192.168.86.42
3 Likes
3

Here you can read about Reserved IP addresses - Wikipedia

2 Likes
4

No worries I figured it out. Thanks for directing me to that website.

3 Likes
5

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.