Quote from: goatpig on Today at 08:31:35 AM

1) Check port 15000 isn't in use.
2) Check ArmoryQt is actually trying to connect to localhost:15000
3) Start ArmoryDB manually if you have to, give it the proper port.

1) Yes, did that using tcpview.

2) ArmoryQT never connects to 15000 even when running properly, only 8223.
At least that's what tcpview showed.

3) Tried this again and it works only if you start armorydb manually first then launch armoryqt.
I haven't tried any transactions yet but everything looks normal.
I guess it's ok as a temporary solution but still would like to know why armoryqt freezes and won't start armorydb on it's own.
Also I noticed that if you launch armoryqt first then start armorydb manually it won't connect to the db and tcpview fills up with system processes using port 9001.