|
Title: 0.90 beta problem Post by: ottuzzi on December 06, 2013, 10:03:08 AM Hi there,
I'm new to armory and 2 days ago I installed 0.90 beta and it was not an easy ride. I have bitcoind listening on a non standard port (8334) and this is correctly stated in bitcoin.conf: I was expecting that armory was reading this info automatically but to let things work I had to manually add --satoshi-port=8334 at armory startup. Am I missing something or this is the intended behaviour? Eventually can you fix it? Thanks Bye Piero Title: Re: 0.90 beta problem Post by: goatpig on December 06, 2013, 10:05:56 AM You shouldn't use a custom bitcoin.conf when you let Armory manage bitcoind. Otherwise manage it yourself and turn off the feature in File > Settings in Armory.
Title: Re: 0.90 beta problem Post by: ottuzzi on December 06, 2013, 11:04:45 AM You shouldn't use a custom bitcoin.conf when you let Armory manage bitcoind. Otherwise manage it yourself and turn off the feature in File > Settings in Armory. Hi, thanks for your response and it does really make sense... but :) But I have satoshi client configured on 8334 to make it reachable from the internet using a forwarding rule on my modem (8333 was already used): by armory definition (as a wallet manager that use satoshi client for network management) this is the starting point. So I'm expecting that armory can read bitcoin.conf and connects directly to my own configured bitcoin client. As an alternative please warn user about not standard bitcoin.conf. Thanks again for your product :) Bye |