Skip to content

cli: cockroach connect mistakenly uses port 443 if the --join flag did not provide a port number #61620

@knz

Description

@knz

The following command:

cockroach connect --num-expected-initial-nodes 2   --init-token abc   --join=192.168.2.10

Fails with

W210308 14:59:03.705454 39 1@server/init_handshake.go:389  [connect,init-tls-handshake,peer=192.168.2.10:] 1  peer CA retrieval error: Post
"https://192.168.2.10/trustInit/
": dial tcp 192.168.2.10:443: connect: connection refused
W210308 14:59:03.705769 1 1@server/init_handshake.go:546  [connect,init-tls-handshake] 2  error from client when connecting to peers (retrying): Post
"https://192.168.2.10/
trustInit/": dial tcp 192.168.2.10:443: connect: connection refused

Notice: the connect command tries to use port 443, whereas the other side was listening on the default RPC port, 26257.

Related to #60632

cc @itsbilal @aaron-crl

Epic: CRDB-6663

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-cli-adminCLI commands that pertain to controlling and configuring nodesA-securityC-bugCode not up to spec/doc, specs & docs deemed correct. Solution expected to change code/behavior.S-3-ux-surpriseIssue leaves users wondering whether CRDB is behaving properly. Likely to hurt reputation/adoption.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions