connect ETIMEDOUT with Quick Start #57

New Issue

Ghost · 2020-08-14T04:11:35Z

Ghost commented

2020-08-14 04:11:35 +00:00

I've been trying all day with the example from the website and it wont work at all.

venko_node | connected!
venko_node | Ready to Serve:
venko_node |     ewkhrwk.xyz
venko_node | [default] store.module: greenlock-store-fs
venko_node | [default] challenges.http-01.module: acme-http-01-standalone
venko_node | [default] renewOffset: -45d
venko_node | [default] renewStagger: 3d
venko_node | [default] accountKeyType: EC-P256
venko_node | [default] serverKeyType: RSA-2048
venko_node | 
venko_node | [default] subscriberEmail: me@lucaszanella.com
venko_node | [default] agreeToTerms: (show notice on use)
venko_node | 
venko_node | ACME Directory URL: https://acme-v02.api.letsencrypt.org/directory
venko_node | 
venko_node | By using this software you (me@lucaszanella.com) are agreeing to the following:
venko_node | ACME Subscriber Agreement: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf
venko_node | Greenlock/ACME.js Terms of Use: https://rootprojects.org/legal/#terms
venko_node | 
venko_node | set greenlockOptions.notify to override the default logger
venko_node | Error cert_issue:
venko_node | connect ETIMEDOUT 165.232.74.82:80
venko_node | code: ETIMEDOUT
venko_node | Error: connect ETIMEDOUT 165.232.74.82:80
venko_node |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
venko_node | Error cert_issue:
venko_node | connect ETIMEDOUT 165.232.74.82:80
venko_node | code: ETIMEDOUT
venko_node | Error: connect ETIMEDOUT 165.232.74.82:80
venko_node |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
venko_node | Error cert_issue:
venko_node | connect ETIMEDOUT 165.232.74.82:80
venko_node | code: ETIMEDOUT
venko_node | Error: connect ETIMEDOUT 165.232.74.82:80
venko_node |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
venko_node | Error cert_issue:
venko_node | connect ETIMEDOUT 165.232.74.82:80
venko_node | code: ETIMEDOUT
venko_node | Error: connect ETIMEDOUT 165.232.74.82:80
venko_node |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)
venko_node | Error cert_issue:
venko_node | connect ETIMEDOUT 165.232.74.82:80
venko_node | code: ETIMEDOUT
venko_node | Error: connect ETIMEDOUT 165.232.74.82:80
venko_node |     at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16)

I've been trying all day with the example from the website and it wont work at all. ``` venko_node | connected! venko_node | Ready to Serve: venko_node | ewkhrwk.xyz venko_node | [default] store.module: greenlock-store-fs venko_node | [default] challenges.http-01.module: acme-http-01-standalone venko_node | [default] renewOffset: -45d venko_node | [default] renewStagger: 3d venko_node | [default] accountKeyType: EC-P256 venko_node | [default] serverKeyType: RSA-2048 venko_node | venko_node | [default] subscriberEmail: me@lucaszanella.com venko_node | [default] agreeToTerms: (show notice on use) venko_node | venko_node | ACME Directory URL: https://acme-v02.api.letsencrypt.org/directory venko_node | venko_node | By using this software you (me@lucaszanella.com) are agreeing to the following: venko_node | ACME Subscriber Agreement: https://letsencrypt.org/documents/LE-SA-v1.2-November-15-2017.pdf venko_node | Greenlock/ACME.js Terms of Use: https://rootprojects.org/legal/#terms venko_node | venko_node | set greenlockOptions.notify to override the default logger venko_node | Error cert_issue: venko_node | connect ETIMEDOUT 165.232.74.82:80 venko_node | code: ETIMEDOUT venko_node | Error: connect ETIMEDOUT 165.232.74.82:80 venko_node | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) venko_node | Error cert_issue: venko_node | connect ETIMEDOUT 165.232.74.82:80 venko_node | code: ETIMEDOUT venko_node | Error: connect ETIMEDOUT 165.232.74.82:80 venko_node | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) venko_node | Error cert_issue: venko_node | connect ETIMEDOUT 165.232.74.82:80 venko_node | code: ETIMEDOUT venko_node | Error: connect ETIMEDOUT 165.232.74.82:80 venko_node | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) venko_node | Error cert_issue: venko_node | connect ETIMEDOUT 165.232.74.82:80 venko_node | code: ETIMEDOUT venko_node | Error: connect ETIMEDOUT 165.232.74.82:80 venko_node | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) venko_node | Error cert_issue: venko_node | connect ETIMEDOUT 165.232.74.82:80 venko_node | code: ETIMEDOUT venko_node | Error: connect ETIMEDOUT 165.232.74.82:80 venko_node | at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16) ```

coolaj86 commented

2020-08-14 06:38:29 +00:00

My guess is that you've got some sort of firewall in place, dropping packets to port 80:

venko_node | connect ETIMEDOUT 165.232.74.82:80

What happens if you run

sudo netcat -l 80

and then try to visit http://165.232.74.82:80 in your browser? Do you see the request come through?

When the Quick Start doesn't work, the problem is either very very early on in the configuration, or more likely somewhere in the platform stack.

My guess is that you've got some sort of firewall in place, dropping packets to port 80: ``` venko_node | connect ETIMEDOUT 165.232.74.82:80 ``` What happens if you run ```bash sudo netcat -l 80 ``` and then try to visit `http://165.232.74.82:80` in your browser? Do you see the request come through? When the Quick Start doesn't work, the problem is either very very early on in the configuration, or more likely somewhere in the platform stack.

coolaj86 changed title from ~~Not working anymore?~~ to connect ETIMEDOUT with Quick Start

2020-08-14 06:39:36 +00:00

Ghost commented

2020-08-14 06:41:28 +00:00

Thanks for the response. I just fixed it. Turns out digital ocean gave me a machine with some problems. Port 80 wouldn't work in any way, and I didn't modify anything, I simply created a machine and tried to run node hello world example on port 80 and it wouldn't work. Recreating the machine made it work.

Ghost closed this issue

2020-08-14 06:41:28 +00:00

Sign in to join this conversation.

No Label

No Milestone

No Assignees

2 Participants

Notifications

Due Date

The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: root/greenlock-express.js#57