Connect ETIMEDOUT, stack=Error: connect ETIMEDOUT

Help
1

My domain is: cloud.itwindow.co.za

I ran this command: ./proxcp-deamon (docker image command)
https://hub.docker.com/r/proxcp/proxcp-daemon-v17-nodev12

It produced this output:

2023-11-23T10:19:22.853Z - info: [PROXCP] Getting SSL certificate from Let's Encrypt - please wait...
ACME Directory URL: https://acme-v02.api.letsencrypt.org/directory
2023-11-23T10:21:40.002Z - info: message=connect ETIMEDOUT 41.161.86.3:80, stack=Error: connect ETIMEDOUT 41.161.86.3:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16), errno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, address=41.161.86.3, port=80, context=cert_issue, subject=cloud.itwindow.co.za, altnames=[cloud.itwindow.co.za, www.cloud.itwindow.co.za]
2023-11-23T10:21:40.003Z - info: message=connect ETIMEDOUT 41.161.86.3:80, stack=Error: connect ETIMEDOUT 41.161.86.3:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16), errno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, address=41.161.86.3, port=80, context=cert_issue, subject=cloud.itwindow.co.za, altnames=[cloud.itwindow.co.za, www.cloud.itwindow.co.za], toJSON=function errorToJSON(e) {
var error = {};
Object.getOwnPropertyNames(e).forEach(function(k) {
error[k] = e[k];
});
return error;
}, servername=cloud.itwindow.co.za, subject=cloud.itwindow.co.za, $ref=$["altnames"], renewAt=1, module=acme-http-01-webroot, webroot=/var/www/html/.well-known/acme-challenge
2023-11-23T10:21:40.004Z - info: message=connect ETIMEDOUT 41.161.86.3:80, stack=Error: connect ETIMEDOUT 41.161.86.3:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16), errno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, address=41.161.86.3, port=80, context=cert_issue, subject=cloud.itwindow.co.za, altnames=[cloud.itwindow.co.za, www.cloud.itwindow.co.za], toJSON=function errorToJSON(e) {
var error = {};
Object.getOwnPropertyNames(e).forEach(function(k) {
error[k] = e[k];
});
return error;
}, servername=cloud.itwindow.co.za, subject=cloud.itwindow.co.za, $ref=$["altnames"], renewAt=1, module=acme-http-01-webroot, webroot=/var/www/html/.well-known/acme-challenge
2023-11-23T10:21:40.005Z - info: message=connect ETIMEDOUT 41.161.86.3:80, stack=Error: connect ETIMEDOUT 41.161.86.3:80
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1144:16), errno=ETIMEDOUT, code=ETIMEDOUT, syscall=connect, address=41.161.86.3, port=80, context=cert_issue, subject=cloud.itwindow.co.za, altnames=[cloud.itwindow.co.za, www.cloud.itwindow.co.za], toJSON=function errorToJSON(e) {
var error = {};
Object.getOwnPropertyNames(e).forEach(function(k) {
error[k] = e[k];
});
return error;
}, servername=cloud.itwindow.co.za, subject=cloud.itwindow.co.za, $ref=$["altnames"], renewAt=1, module=acme-http-01-webroot, webroot=/var/www/html/.well-known/acme-challenge

My web server is (include version): apache

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

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

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

2

I have no experience with that ACME client but it looks to be using an HTTP Challenge to get the cert.

The error message is not from Let's Encrypt but there is clearly a comms problem to or from your container. Right now I cannot reach your domain using HTTP which is required for the HTTP Challenge.

I also see you got a cert yesterday but just for the main domain name (not with the www subdomain).

Are you still having problems? The Let's Debug test site is helpful when setting up new web services

https://letsdebug.net

3 Likes
3

I shutdown the server, trying to resolve this issue (creating a new server at the moment), thats why you cant access HTTP at the moment.

however, when it was online I cloud access HTTP via public.

Ill respond to this post once I get the error again.

yes, I did x2 renewals yesterday on cloud.

thank you

2 Likes
4

nothing yet...

curl -Ii cloud.itwindow.co.za
curl: (56) Recv failure: Connection reset by peer

curl -Ii www.cloud.itwindow.co.za
curl: (56) Recv failure: Connection reset by peer
3 Likes
5

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