I port forwarded 80 and 443 to the IP of my server behind my router. To my knowledge my internet provider does not block 80 or 443, in fact I switched from my old provider because they did block 80 and 443. However I’m still getting this failed challenge error. I have a feeling it might be due the U…

Is ufw enabled? Check what this says: sudo ufw status verbose If it is active and incoming connections are blocked, enable appropriate port as follows: sudo ufw allow XXX/tcp where XXX is 443 for HTTPS or 80 for HTTP.

Hello there! This is the output of sudo ufw status To Action From -- ------ ---- 22 ALLOW IN Anywhere 80/tcp ALLOW IN Anywhere 64738 ALLOW IN Anywhere 137,138/udp (Sa…

[image] wh33t: Do I need to have 443 in there too? Yes, indeed :slight_smile: P.S. That is if you are using TLS-SNI verification. For HTTP verification you would only need port 80 open and for DNS verification you would not need open ports at all (but you would have to be able to add TXT rec…

So letsencrypt requires 443 and 80 to both be open for install to work properly? I did figure that 443 would have to be open to actually hit the webserver on https.

See the edit above - 443 is needed for this particular type of verification you have used (TLS-SNI) :wink: You can try HTTP or DNS verifications instead if you like (DNS is supported by some alternative clients - Perl, Go and Bash ones as far as I know).

[image] leader: DNS is supported by some alternative clients - Perl, Go and Bash ones as far as I know Since yesterday, Certbot 0.9.0 release supports DNS challenge too :wink:

[image] sahsanu: Since yesterday, Certbot 0.9.0 release supports DNS challenge too Bah, I must have missed that. :tada::wine_glass: :+1:

Hrm, I’m still getting the same error message. Do I need to enable SSL and such in my .conf file? Maybe I am mistaken in believing that letsencrypt would do that for me?

[image] wh33t: Maybe I am mistaken in believing that letsencrypt would do that for me? Nope, that's correct. The apache plugin should enable SSL in your configuration. I would recommend verifying basic connectivity to port 443 anyway, you can listen on port 443 with something like nc -k -l l…

Could it be because I’m using a dynamic domain from dynu.net ?

Does letsencrypt require a UFW rule? Ubuntu 16.04LTS

Help

sahsanu October 6, 2016, 10:53pm 7

Since yesterday, Certbot 0.9.0 release supports DNS challenge too

Topic		Replies	Views
Trying to encrypt traffic on a small home based webserver Help	5	2790	June 24, 2016
Make Sure UFW Has Port 443 Open........Secure handshake Server	0	1517	December 23, 2016
Failed to connect to -x-x-x-x-443 for tlssni-01 challenge Server	8	1966	October 31, 2016
Failed to connect to *:443 for TLS-SNI-01 challenge Help	15	4832	April 6, 2017
Letsencrypt --apache error Help	22	4205	April 13, 2017

Does letsencrypt require a UFW rule? Ubuntu 16.04LTS

Related topics