Title: Armory Not Talking to Bitcoin engine. Post by: cosmo1957 on October 07, 2021, 09:15:35 AM ## UPDATE: 7Oct21 @ 10.24pm:
After several restarts and option changes, I have managed to get Armory 96.5 working with Bitcoin engine 0.21.1 Armory 96.3 must use a command line option to change the data directory: -- "C:\Program Files (x86)\Armory\ArmoryQt.exe" --datadir="E:\Crypto_Storage\Armory" Armory 96.5 allows this data directory to be set via the user interface. However, it does not work. I have to use the same command line option to get Armory 96.5 to work. Can anyone else confirm this non-function ? Thanks. ## Original: Hi, I upgraded from Armory 96.3 to 96.5 When I started Armory, the wallet check is ok, but not talking to bitcoin engine (0.21.1). . I reinstalled Armory 96.3 and the same problem. I tried running Bitcoin engine standalone first, and also letting Armory manage bitcoin engine. Armory is still not talking to bitcoin engine. . In summary, Bitcoin engine runs ok and Armory runs ok, but not talking. Any suggestions ? Thanks. end. Title: Re: Armory Not Talking to Bitcoin engine. Post by: nc50lc on October 08, 2021, 05:06:18 AM ## UPDATE: 7Oct21 @ 10.24pm: I've tried it, changed the setting in the GUI = "Armory Database Dir: <to my Armory datadir>",-snip- Armory 96.5 allows this data directory to be set via the user interface. However, it does not work. I have to use the same command line option to get Armory 96.5 to work. Can anyone else confirm this non-function ? Thanks. -snip- then removed the pathing settings in my armoryqt.conf file (same as the command line option). And it indeed used the default Armory datadir. Title: Re: Armory Not Talking to Bitcoin engine. Post by: HCP on October 13, 2021, 01:32:31 AM Is this specifically the Armory Database directory... or is it ignoring the Bitcoin Home Dir as well? ???
Title: Re: Armory Not Talking to Bitcoin engine. Post by: nc50lc on October 13, 2021, 03:52:38 AM Bitcoin Home Directory setting works in the GUI at my end.
But I'm puzzled how did that fixed the issue since it's he mentioned both work, while it's just a "not talking" or connection error where it's usually an RPC connection issue. Can't tell without his reply. |