-
Notifications
You must be signed in to change notification settings - Fork 377
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
Bug: invalid URL 'http://[fd01::4]:8332': invalid port #792
Comments
Investigating into the Rust dependency chain, I've stumbled upon these issues: apoelstra/rust-jsonrpc#62 The line that prints the error message is probably this one: https://github.com/apoelstra/rust-jsonrpc/blob/master/src/simple_http.rs#L199 I'm still looking into where the "invalid port" reason message is coming from. |
It seems like an outdated version of jsonrpc without IPv6 support is being pulled via Cargo dependencies:
jsonrpc 0.13.0 would have IPv6 support – is it possible to overload versions of transitive dependencies with Cargo? Then this would probably be an easy fix. |
It should be possible to patch it - add this to [patch.crates-io.bitcoincore-rpc]
git = "https://github.com/rust-bitcoin/rust-bitcoincore-rpc"
# May minimize the chance of breaking, you can try to leave it out to get even more recent bitcoincore-rpc
branch = "d2959ec11b951f304a538b2bbab67d999cdb3426" |
@Kixunil Thanks! The branch doesn't seem to exist, but I simply removed it (so it used bde02d7f / master) and it seems to work. |
This bug is still present in version 0.9.11. |
Indeed, we need a new release of |
Describe the bug
If the bitcoind address resolves to an IPv6 address, an invalid URL is being constructed:
http://[fd01::4]:8332
Either that, or the URL is in fact valid but some component within electrs can't deal with it and outputs the message:
Electrs version
electrs 0.9.10 running within Docker 20.10.12 under Ubuntu 22.04.1 LTS (all up to date)
To Reproduce
Steps to reproduce the behavior:
Expected behavior
An IPv6 connection to bitcoind, just like with IPv4.
Configuration
The relevant part of the config is probably:
The text was updated successfully, but these errors were encountered: