Failed to establish GRPC connection to AceMlc2 service: failed to start grpc connection with address ace.eu.hawkeye.services-edge.paloaltonetworks.com

[CyberEye]

Getting below alert from the hardware firewall.

"Failed to establish GRPC connection to AceMlc2 service: failed to start grpc connection with address ace.eu.hawkeye.services-edge.paloaltonetworks.com:443"

Followed the below document but no luck. Does anyone faced similar issue ?

https://knowledgebase.paloaltonetworks.com/KCSArticleDetail?id=kA14u000000g1DOCAY&lang=en_US%E2%80%A...

[JayGolf]

Hi @CyberEye ,

Do you have an IoT license? The grpc is used to interface with an IoT cloud tenant. 

[CyberEye]

No IOT is not configured

[gshort]

Take a look at the command 'show ctd-agent status security-client'. This should give some details of why it is failing along with the current connection status along with the server that it is trying to connect to.

Make sure you have a valid Device Certificate and the Management Interface/service route (Palo Alto Network Services) is able to reach the the URL(s) being called.

Also ensure that the OCSP urls that Palo Alto uses are also accessible over port 80:

• http://ocsp.paloaltonetworks.com
• http://crl.paloaltonetworks.com
• http://ocsp.godaddy.com
• http://crl.godaddy.com

[MP18]

Here is the fix run the below command for CLI

set system setting ctd feature-forward mica disable