Armory stuck in offline mode 0.94.1 beta

[tsr.nc2]

I am using arch Linux. I can connect using bitcoin-qt. Armory starts up and connects to bitcoind and confirms the blockchain, then after reading the blockchain it claims it is offline and it could not detect internet connection. I have tried the --skip-online-check to with no change. However it does say connected 0 blocks in the bottom right corner.

Armory log
http://www.filehosting.org/file/details/578171/EQkeVEgbpY3YUbAu/armorylog_20160617_0837.txt

[goatpig]

Can't see the log file on that site, please use pastebin instead.

The connection is Armory trying to get ahold of your bitcoin node through p2p. It needs to be able to talk to localhost:8333. Either that or you didn't point it at the correct blockchain data folder (use --satoshi-datadir)

[tsr.nc2]

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.

[goatpig]

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.

You shouldn't set your RPC port to 8333, that's the P2P port.