Here is a new log file. The log is too big and pastbin will not accept it. I hope this site works for you.
http://filebin.ca/2lFIroguz2BW/armorylog_20160617_0837.txt
adding these lines to bitcoin.conf
rpcport=8333
rpcconnect=127.0.0.1
results in armory not being able to start bitcoind and a new error
however using rpcport=8332(the defalt) allows bitcoind to start.
Is there anyway to make armory use the 8332 port?
bitcoin-cli can connect on the 8332 port.
My bitcoin.conf file does contain 2 lines added by armory
rpcuser=generated_by_armory
rpcpassword= *****Random text here*******
running armory as root has no effect so I do not believe it is a permission thing, unless armory auto drops root permission. Any help would be nice as I have some funds tied up in this wallet at the moment.
I have found a Solution. Manually starting bitcond with the 8332 port and in armory unchecking "Let Armory run Bitcoin-Core in the background" allowed armory to connect. It would be nice if armory could handle bitcoind for me but not that big a deal.
http://filebin.ca/2lFIroguz2BW/armorylog_20160617_0837.txt
adding these lines to bitcoin.conf
rpcport=8333
rpcconnect=127.0.0.1
results in armory not being able to start bitcoind and a new error
however using rpcport=8332(the defalt) allows bitcoind to start.
Is there anyway to make armory use the 8332 port?
bitcoin-cli can connect on the 8332 port.
My bitcoin.conf file does contain 2 lines added by armory
rpcuser=generated_by_armory
rpcpassword= *****Random text here*******
running armory as root has no effect so I do not believe it is a permission thing, unless armory auto drops root permission. Any help would be nice as I have some funds tied up in this wallet at the moment.
I have found a Solution. Manually starting bitcond with the 8332 port and in armory unchecking "Let Armory run Bitcoin-Core in the background" allowed armory to connect. It would be nice if armory could handle bitcoind for me but not that big a deal.
You shouldn't set your RPC port to 8333, that's the P2P port.
