Error with command "etcdctl --endpoints=IP1:2379,IP2:2379,IP3:2379 member list" #16303

siddhu1409 · 2023-07-20T17:26:04Z

siddhu1409
Jul 20, 2023

Bug report criteria

This bug report is not security related, security issues should be disclosed privately via [email protected].
This is not a support request, support requests should be raised in the etcd discussion forums.
You have read the etcd bug reporting guidelines.
Existing open issues along with etcd frequently asked questions have been checked and this is not a duplicate.

What happened?

I have a 3 node cluster. I have added Node 1 after removing node 1 with different IP. Now On node 0 and node 2 command is working fine while node 1 is giving error for below command.

[root@IP2 ~]# etcdctl member list
4e40bb9723e4c6c8, started, etcd0, http://IP1:2380, http://IP1:2379, false
707fa5277a3151ac, started, etcd1, http://IP2:2380, http://IP2:2379, false
bb9e47b4f1319429, started, etcd2, http://IP3:2380, http://IP3:2379, false

[root@IP2 ~]# etcdctl --endpoints=IP1:2379,IP2:2379,IP3:2379 member list
{"level":"warn","ts":"2023-07-20T22:26:23.959+0530","logger":"etcd-client","caller":"[email protected]/retry_interceptor.go:62","msg":"retrying of unary invoker failed","target":"etcd-endpoints://0xc0001cc000/IP1:2379","attempt":0,"error":"rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = "transport: Error while dialing failed to do connect handshake, response: \"HTTP/1.1 403 Tunnel or SSL Forbidden\\r\\nConnection: close\\r\\nContent-Length: 666\\r\\nCache-Control: no-store\\r\\nContent-Language: en\\r\\nContent-Type: text/html\\r\\nDate: Thu, 20 Jul 2023 16:56:23 GMT\\r\\nVia: 1.1 NOIDA-APP-PROXY-WCG\\r\\n\\r\\n<TITLE>Tunnel or SSL Forbidden</TITLE>\\n<BODY BGCOLOR=\\\"white\\\" FGCOLOR=\\\"black\\\">

Tunnel or SSL Forbidden

\\n<FONT FACE=\\\"Helvetica,Arial\\\">\\nDescription: 2379 is not an allowed port for Tunnel or SSL connections\\n

\\n\\n\\n \\x00\"""}
Error: context deadline exceeded

Can anyone help me to undestand the error?

What did you expect to happen?

It should return member list.

How can we reproduce it (as minimally and precisely as possible)?

Remove a node with name Node1
Add a new node with different IP and same name Node 1
now try to run the command

Anything else we need to know?

No response

Etcd version (please run commands below)

$ etcd --version
etcd Version: 3.5.6
Git SHA: cecbe35ce
Go Version: go1.16.15
Go OS/Arch: linux/amd64

$ etcdctl version
etcdctl version: 3.5.6
API version: 3.5


</details>


### Etcd configuration (command line flags or environment variables)

<details>

# paste your configuration here

</details>


### Etcd debug information (please run commands below, feel free to obfuscate the IP address or FQDN in the output)

<details>

```console
$ etcdctl member list -w table
# paste output here

$ etcdctl --endpoints=<member list> endpoint status -w table
# paste output here

Relevant log output

No response

fuweid · 2023-07-23T07:47:14Z

fuweid
Jul 23, 2023
Maintainer

So you are using old IP1 to reconnect? It seems that you were connecting to wrong IP

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Error with command "etcdctl --endpoints=IP1:2379,IP2:2379,IP3:2379 member list" #16303

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Error with command "etcdctl --endpoints=IP1:2379,IP2:2379,IP3:2379 member list" #16303

Uh oh!

siddhu1409 Jul 20, 2023

Bug report criteria

What happened?

Tunnel or SSL Forbidden

What did you expect to happen?

How can we reproduce it (as minimally and precisely as possible)?

Anything else we need to know?

Etcd version (please run commands below)

Relevant log output

Replies: 1 comment

Uh oh!

fuweid Jul 23, 2023 Maintainer

siddhu1409
Jul 20, 2023

fuweid
Jul 23, 2023
Maintainer