Quote from: etotheipi on October 29, 2012, 03:16:23 AM

Quote from: inglian on October 29, 2012, 02:39:22 AM

My first attempt at broadcasting an offline transaction with Armory kept silently failing. Logs show "ConnectionError: Connection to localhost DNE" despite Armory showing "Connected" status on the main screen and current block number.

This problem has come up quite a few times in the past, but it was so long ago I honestly don't remember if it was ever resolved. However, there have been some networking-related bug fixes since then. Please download 0.82.4 and try again: https://github.com/etotheipi/BitcoinArmory/downloads

I installed https://github.com/downloads/etotheipi/BitcoinArmory/armory_0.82.4-alpha_win32_and_win64.msi which runs for a few seconds and then silently dies without logging anything. Same immediately after a reboot with bitcoin-qt running and up to date on blockchain. Any troubleshooting I should do?

Quote from: psy on October 29, 2012, 06:08:46 AM

inglian, are your network connections limited on bitcoin.conf? If so, take out the limit.
I faced similar problems when I had the number of connections limited to 25, so Armory would only connect to the bitcoin client when one of the regular network clients dropped it's connection.

Connections are default (125), though with NAT I have none incoming and just my default 8 outgoing. So I should be able to accept another 117 connections locally.

Thanks to you both for the help.