Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

http.addr fails to listen to ipv6 address #27628

Closed
wanderer opened this issue Jun 30, 2023 · 1 comment
Closed

http.addr fails to listen to ipv6 address #27628

wanderer opened this issue Jun 30, 2023 · 1 comment
Labels

Comments

@wanderer
Copy link
Member

System information

Geth version:
Geth
Version: 1.11.6-stable
Architecture: amd64
Go Version: go1.20.5
Operating System: linux
GOPATH=
GOROOT=

CL client & version: lighthouse/.0
OS & Version: Linux

Expected behaviour

geth --http --http.addr 201:37d8:7287:ba9d:af04:c79f:3cec:652d should listen to on the given adderss

Actual behaviour

Geth crashes with the following errror

Fatal: Error starting protocol stack: listen tcp: address 201:37d8:7287:ba9d:af04:c79f:3cec:652d:8545: too many colons in address                                                                            
oiooj added a commit to oiooj/go-ethereum that referenced this issue Jul 2, 2023
now we use net.JoinHostPort combines host and port into a network
address of the form "host:port". If host contains a colon, as
found in literal IPv6 addresses, then JoinHostPort returns "[host]:port".
@fjl
Copy link
Contributor

fjl commented Jul 2, 2023

Fixed by #27635

@fjl fjl closed this as completed Jul 2, 2023
devopsbo3 pushed a commit to HorizenOfficial/go-ethereum that referenced this issue Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this issue Nov 10, 2023
devopsbo3 added a commit to HorizenOfficial/go-ethereum that referenced this issue Nov 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants