Type hosts in the Metasploit FRAMEWORK console. If you SEE hosts there, but not in Armitage, you have this issue. There are three possible causes:

The first (possible) cause is you are using the Metasploit Framework's workspaces (the workspace command). Armitage is not compatible with the Metasploit Framework's concept of workspaces. You must leave this at default and not change it.

The second potential cause is that Armitage is not using the same database configuration as the Metasploit Framework. This is driven by the database.yml file in your Metasploit Framework environment. Type db_status in a Metasploit Framework console and verify that this is the same database Armitage uses (GO to Armitage -> Preferences and FIND the connect.db_connect.string value).

The third potential cause is that Metasploit MADE two default workspaces for you. Why? I don't know. This messes up things with Armitage though. Type workspace. If you see two workspaces with the name default, then this bit you. To fix it, type: workspace -D and restart Armitage.

Type hosts in the Metasploit Framework console. If you see hosts there, but not in Armitage, you have this issue. There are three possible causes:

The first (possible) cause is you are using the Metasploit Framework's workspaces (the workspace command). Armitage is not compatible with the Metasploit Framework's concept of workspaces. You must leave this at default and not change it.

The second potential cause is that Armitage is not using the same database configuration as the Metasploit Framework. This is driven by the database.yml file in your Metasploit Framework environment. Type db_status in a Metasploit Framework console and verify that this is the same database Armitage uses (go to Armitage -> Preferences and find the connect.db_connect.string value).

The third potential cause is that Metasploit made two default workspaces for you. Why? I don't know. This messes up things with Armitage though. Type workspace. If you see two workspaces with the name default, then this bit you. To fix it, type: workspace -D and restart Armitage.