You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Great work! I especially appreciate the ability to change the UID/GID via build-arg.
I have setup a Bitcoin-Full-Node and an Electrum Rust Server, wich is working fine on clearnet.
When I setup a tor-proxy-container and specify proxy=torproxy:9050 in bitcoin.conf, electrs can no longer access ELECTRS_DAEMON_P2P_ADDR=bitcoind:8333 which makes sense, because this is supposed to be only accessible via the tor network.
Is there an obvious solution to my problem, where I can proxy bitcoind-traffic through tor and still access bitcoind:8333 locally?
Great work! I especially appreciate the ability to change the UID/GID via build-arg.
I have setup a Bitcoin-Full-Node and an Electrum Rust Server, wich is working fine on clearnet.
When I setup a tor-proxy-container and specify
proxy=torproxy:9050
inbitcoin.conf
, electrs can no longer accessELECTRS_DAEMON_P2P_ADDR=bitcoind:8333
which makes sense, because this is supposed to be only accessible via the tor network.Is there an obvious solution to my problem, where I can proxy bitcoind-traffic through tor and still access
bitcoind:8333
locally?Thanks!
docker-compose.yml
:bitcoin.conf
:EDIT:
electrs error message
:The text was updated successfully, but these errors were encountered: