This message was deleted.
# general
a
This message was deleted.
👍 1
🤔 1
l
@creamy-pencil-82913 @nutritious-tomato-14686 any thoughts on this
h
all other imports worked but the one behind corporate network did not.. you need to make sure traffic is allowed - if there is any firewall in between https://docs.k3s.io/installation/requirements#inbound-rules-for-k3s-nodes
is the k3s cluster on corporate network behind a NAT ?
you need to work with your corporate network and firewall teams
l
yes able to ping via rancher-agent pod https://rancher.ms.ai\ and it is reaching only cert issue
only i am getting the below error, anything the client have setup like ssl cert level security inside worker nodes ? so i need to whitelist the ssl cert of https://rancher.ms.ai is that make sense ?
Copy code
Certificate chain is not complete, please check if all needed intermediate certificates are included in the server certificate (in the correct order) and if the cacerts setting in Rancher either contains the correct CA certificate (in the case of using self signed certificates) or is empty (in the case of using a certificate signed by a recognized CA). Certificate information is displayed above. error: Get \"
<https://rancher.ms.ai>\":
tls: failed to verify certificate: x509: certificate signed by unknown authority"
or it has any hack to ignore the cerificate chain check ??
successfully fixed by adding the CA certs of the agent nodes to Rancher server cacerts now i am having a new issue
Copy code
Failed to connect to proxy. Empty dialer response" error="read tcp 10.42.0.7:57750-> <rancher UI public ip>:443: read: connection reset by peer"

msg="Remotedialer proxy error" error="read tcp 10.42.0.7:47514-><rancher UI public ip>:443: read: connection reset by peer"
i can able to telnet from the node to
<rancher UI public ip>:443
any help or suggestions most appreciated !!!
🎉 1
@creamy-pencil-82913 hi , i hope the error is coming from -> https://github.com/rancher/remotedialer/blob/afe97852fef44f4b9955bd7563021dee52c2061d/client.go#L22 how to trouble shoot this ?