We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
zmqpubrawtx
rpcbind
dashd can be bound to multiple interfaces with rpcbind, but not with zmqpubrawtx.
dashd
dash.conf:
dash.conf
txindex=1 addressindex=1 timestampindex=1 spentindex=1 [main] rpcuser=app rpcpassword=hackmeplzkthx # localhost bind=127.0.0.1:9999 rpcbind=127.0.0.1:9998 rpcconnect=127.0.0.1:9998 rpcallowip=127.0.0.1/16 zmqpubrawtx=tcp://127.0.0.1:28332 zmqpubrawtxlock=tcp://127.0.0.1:28332 # LAN bind=10.11.5.104:9999 rpcbind=10.11.5.104:9998 rpcconnect=10.11.5.104:9998 rpcallowip=10.11.5.104/24 zmqpubrawtx=tcp://10.11.5.104:28332 zmqpubrawtxlock=tcp://10.11.5.104:28332
I've run with the # localhost section first and can confirm that I can access ZMQ via localhost, but not my LAN address.
# localhost
localhost
I've also moved the # LAN section first and confirmed that the opposite is true.
# LAN
In both cases, RPC can be accessed from either network as expected.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
dashd
can be bound to multiple interfaces withrpcbind
, but not withzmqpubrawtx
.dash.conf
:I've run with the
# localhost
section first and can confirm that I can access ZMQ vialocalhost
, but not my LAN address.I've also moved the
# LAN
section first and confirmed that the opposite is true.In both cases, RPC can be accessed from either network as expected.
The text was updated successfully, but these errors were encountered: