Re: Armory-Transaction through BitcoinCore running as TOR-hidden-service

@sackot: Cheers mate! Found that option but I took a different path.

@goatpig: Thank you very much for taking the time!

Somehow I figured out it has something to do with the JSON calls from Armory to Bitcoin Core RCP, that are somehow obstructed by the TOR-settings.

I added
rpcallowip=127.0.0.1
to the bitcoin.conf to ensure calls form Armory go through

I also read somewhere that port 127.0.0.1:8334 is used for RPC calls to Bitcoin Core, because Tor is using this port as well.

I'm now able to run bitcoind -daemon independently of Armory as long I immediately start Armory after I started bitcoind -daemon.
I guess that once bitcoind has established to many connections it doesn't accept RCP calls form Armory anymore.
Just peering through the fog

I have now sent my first test transaction. Got that Warning

Quote

Your Transaction failed to broadcast through the P2P layer but successfully broadcasted through the RPC. This can be a symptom of bad node connectivity to the Bitcoin network, or that your node is overwhelmed by network traffic. If you consistently get this warning, report to the developers for assistance with node maintenance.

So the RPC call seemed to have worked. Have got one confirmation so far.