Console-to-Engine Communication Failed (AzureVM Scan Engine)

Hey everyone,

I spawned a AzureVM according
Azure Scan Engines | InsightVM Documentation (
and want to use the Standard Console to Engine sync.

Does someone have an idea, why I’m getting this error?
2022-05-04T11:51:10 [INFO] [Thread: NSEManager] Accepted console connection from XX.XX.XX.XX:60048->YY.YY.YY.YY:40814
2022-05-04T11:51:10 [INFO] [Thread: NSC @ XX.XX.XX.XX:60048->YY.YY.YY.YY:40814] Console connection XX.XX.XX.XX:60048 encrypted using NONE with SSL_NULL_WITH_NULL_NULL
2022-05-04T11:51:10 [WARN] [Thread: NSC @ XX.XX.XX.XX:60048->YY.YY.YY.YY:40814] Failure while communicating with the console XX.XX.XX.XX:60048.
java.lang.RuntimeException: peer not authenticated
at Source) ~[r7shared.jar:na]
at com.rapid7.nexpose.nse.NSEManager$NSEConnection.initConnection(Unknown Source) [nse.jar:na]
at com.rapid7.nexpose.nse.NSEManager$ Source) [nse.jar:na]
Caused by: peer not authenticated
at ~[na:1.8.0_252]
… 3 common frames omitted

After the failed sync, also no console.xml is created at the AzureUbuntuRapid7VM.


were you able to resolve this ? I have set up the azure scan engine with inbound rules using gateway address for my scan console (my scan console has a 10.x.x.x address). I do see a traffic allowed entry when I try to define my scan engine in the admin page of the Security console. But the consoles.xml does not get created in my azure scan engine and I get a in the nsc.log