Certbot failed with error code (1) Topic is solved

[Lorem]

Hello again!

I've decided I'd probably like to access Nextcloud outside of my home so decided to setup SSL following @Joulinar's very helpful guidelines on another post!

I've set up a domain via no-ip, installed this onto the Pi and checked the IP updates successfuly.
I've then logged into my router (ZTE) and configured port forwarding for 80 and 443 with my LAN IP.

When I run dietpi-letsencrypt and initiate I get 'Certbot failed with error code (1)'

Code: Select all

Domain: XXXXXXXX.hopto.org
   Type:   connection
   Detail: Fetching
   http://XXXXXXXXX.hopto.org/.well-known/acme-challenge/PsZVYR5deG1BHIYF4Eaq3eCe04urXXXvweJ7ZCDGBzlEuN8:
   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.
[FAILED] Certbot failed with error code (1), please check its terminal output. Aborting...

As far as I'm aware I've set it up as instructed, I've also set firewall settings to 'Low' as opposed to the previous 'High' thinking this could help based on the above.

Thanks in advance!

[Joulinar]

Hi,

1. Can you check if your system is reachable via DDNS on port 80/http from internet? This is something that would need to work to get a certificate created.
2. As well you can check on NoIP website if your IP address was correctly registered.
3. To double check, you have forwarded port 80/443 TCP (not UDP) on your router?
4. Do you have a VPN client running on your DietPi device?

[Lorem]

Hi @Joulinar!

I've had a little play and can only access the NOIP Link when the IP it points to is the local ip of the Pi (ie 192.168.1.123) – once it updates to the dynamic IP it doesn't work anymore.

No VPN is running on the device

Thanks
L

[Joulinar]

Do you have forwarded port 80/443 TCP (not UDP) on your router to DietPi device?

[Lorem]

I believe so. I''ve forwarded port 80 and 443 to the Pi's LAN IP.
I'm on 64bit - could this have anything to do with the error?

[Joulinar]

this should not matter. do you have any firewall or additional security software installed?

Pls can you double check port forwarding on your router

[Lorem]

No additional security installed and I've set firewall settings to Low on my Router / Macbook.
Port forwarding is set up – my ISP said I need a static IP for this to work but I presume NO IP solves this problem?

Thanks

[Joulinar]

Can you check if external IP on your internet router is same as the one registered at NoIP? Can you check if you are able to access your system using the external IP directly?

[Lorem]

All resolved – Turns out my ISP was using CG-NAT so I had to purchase a static IP.
All working now!
Thanks again for the help

[Joulinar]

ah ok, good that you found it. To bad that you need to purchase something in addition.