This message was deleted.
# puppet-enterprise
s
This message was deleted.
b
are you sure port 8140 is open and reachable fro your client?
c
What version number does
puppet --version
show?
"client hello" is the first message in the TLS handshake, so a failure there usually indicates the server, or a proxy that intercepted the connection, does not like the handshake parameters for some reason.
e
version 7.24.0 and the compiler by that port is accesible in test-netconnection
c
test-netconnection
only indicates that the port is accessible via TCP. It provides no information on TLS.
e
Hello Again,
Looks this is showing off again and in will need any recomendation, validation commands, etc PS C:\Windows\system32> puppet agent -t Error: Connection to https://compile.xxx.xxx.com:8140/puppet-ca/v1 failed, trying next route: Request to https://compile.xxx.xxx.com:8140/puppet-ca/v1 failed after 44.518 seconds: An existing connection was forcibly closed by the remote host. - SSL_connect Wrapped exception: An existing connection was forcibly closed by the remote host. - SSL_connect Error: No more routes to ca Error: No more routes to ca
b
is puppetserver up and running on compile....com?
e
yes, i have thousand of server working ok, like 5 with this for a long time,
Last time i was trying with the Tsl configuration but not results from that approach,
Any idea, recomandation, where to look, windows is not my area of expertise, so anything is valid
b
can you create a TLS connection with curl or something? did you check the puppetserver logfiles?
when there are thousand systems connecting to a single puppetserver, it could be overloaded