-
Notifications
You must be signed in to change notification settings - Fork 35.5k
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
Default behavior of binding to all interfaces for RPC server not working #9272
Comments
Are you sure this is really the case? That message:
Means that it can't bind on 0.0.0.0 - which usually means that the IPv6 any address works as 'catchall' for both incoming IPv4 and IPv6 connections. This is the case on some OSes, making it unnecessary to have two binds. Have you tried connecting to the port? |
BTW: the default behavior is, and always has been, to bind on all interfaces if |
I've just faced the same problem. Maybe it's worth noting this behavior in bitcoind help? Because although the behavior has always been such, the option is unambiguously described that it binds to all interfaces by default:
I had to google some more time to find out an answer. |
Also should close bitcoin#9272
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
fa0119a doc: Refer in rpcbind doc to the manpage (MarcoFalke) Pull request description: The help was outdated, so refer to the updated manpage instead. * closes bitcoin#14740 * closes bitcoin#9272 ACKs for top commit: emilengler: Concept ACK fa0119a laanwj: ACK fa0119a fanquake: ACK fa0119a Tree-SHA512: 9836e4f31ece7acae334b47e3104b4595d0d1c1977af386a9463faf49aea9de3ab1c1dc3de248d0ee09e3b13693eaf6902dc82d277062e1bb1980b1117236fbb
Describe the issue
The
--help
forrpcbind
suggests that the default behavior is to bind to all interfaces. However, in Core 0.13.1, I noticed that if rpcbind is left out of the config, the RPC server is either only bound to the loopback interface or only bound to the IPv6 port.Can you reliably reproduce the issue?
Yes. It fails differently, depending on whether or not you've supplied
rpcallowip
Reproduction Scenario 1
Fails silently, only binds to loopback interface.
Reproduction Scenario 2
Error message in log, only binds to all interfaces for IPv6.
Binding RPC on address 0.0.0.0 port 8332 failed.
reported in debug.log.What version of bitcoin-core are you using?
0.13.1
Machine specs:
The text was updated successfully, but these errors were encountered: