[Request] Option to bind bitcoind's JSON-RPC server to a specific IP

[aceat64]

Now that the JSON-RPC server is secured by a username and password (although not encrypted), I would really like the option of being able to bind bitcoind to another IP and/or port. For example, I have a handful of nodes that all have a public interface and a local interface. I would like to be able to bind bitcoind to an IP on my internal interface so that I can monitor and manage the node from one server.

[1714866694]

1714866694

[1714866694]

1714866694

[jgarzik]

Now that the JSON-RPC server is secured by a username and password (although not encrypted), I would really like the option of being able to bind bitcoind to another IP and/or port. For example, I have a handful of nodes that all have a public interface and a local interface. I would like to be able to bind bitcoind to an IP on my internal interface so that I can monitor and manage the node from one server.

Really, it should bind to *, and then filter out requests from addresses other than those on a filter-list.

[nimnul]

Binding to specific interfaces and ports is still a good idea as default JSON-RPC port can be already taken by someone else.

+1