# K3s with etcd: nodes cannot connect to first node **URL:** \ **Category:** k3s, k3OS, and k3d\ **Created:** [October 8, 2020, 10:09am UTC](https://forums.suse.com/t/k3s-with-etcd-nodes-cannot-connect-to-first-node/18531 "2020-10-08T10:09:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![dalo](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@dalo](https://forums.suse.com/u/dalo)\ **Post date:** [October 8, 2020, 10:09am UTC](https://forums.suse.com/t/k3s-with-etcd-nodes-cannot-connect-to-first-node/18531/1 "2020-10-08T10:09:23Z")
Im trying to install the latest k3s with the embedded etcd DB. On the first node I run: > curl -sfL [https://get.k3s.io](https://get.k3s.io) | INSTALL\_K3S\_CHANNEL=latest sh -s - --write-kubeconfig-mode 644 --cluster-init --token blah this runs without an error. On the second node I do: > curl -sfL [https://get.k3s.io](https://get.k3s.io) | INSTALL\_K3S\_CHANNEL=latest sh -s - --server [https://192.168.0.118:6443](https://192.168.0.118:6443) --token blah this stops at: > [INFO] systemd: Starting k3s on the first node I get the following errors: > Oct 08 10:01:47 k3s-04 k3s[14754]: failed to reach the peerURL([https://192.168.0.119:2380](https://192.168.0.119:2380)) of member a34017653b7bf464 (Get "[https://192.168.0.119:2380/ve](https://192.168.0.119:2380/ve)\> > Oct 08 10:01:47 k3s-04 k3s[14754]: cannot get the version of member a34017653b7bf464 (Get “[https://192.168.0.119:2380/version](https://192.168.0.119:2380/version)”: Forbidden) > Oct 08 10:01:50 k3s-04 k3s[14754]: health check for peer a34017653b7bf464 could not connect: Forbidden If I do a “curl [https://localhost:2380/version](https://localhost:2380/version)” on the second node I get a “connection refused”. The same command with the stable version works. Does anybody know where I’m stuck here? ---
**Author:** ![dalo](https://avatars.discourse-cdn.com/v4/letter/d/e79b87/32.png) [@dalo](https://forums.suse.com/u/dalo)\ **Post date:** [October 15, 2020, 8:10am UTC](https://forums.suse.com/t/k3s-with-etcd-nodes-cannot-connect-to-first-node/18531/2 "2020-10-15T08:10:36Z")
Issue was a lowercase no\_proxy Variable, set to uppercase NO\_PROXY and it works.