Hello Renan, You may need to check your firewall configuration once more. - Need to check the wildfire action, data-filtering profile, security rule where it should be apply. A KB document for your reference: How to Configure WildFire FYI: WildFire CLI commands Once the basic configuration is complete, the following commands provide the details of the best server selected. To test the Connectivity, follow the steps below: > test wildfire registration This test may take a few minutes to finish. Do you want to continue? (y or n) Test wildfire wildfire registration: successful download server list: successful select the best server: va-s1.wildfire.paloaltonetworks.com Initial registration can only be done on the active unit in an Active/Passive cluster. Note: Do not use PING to test connectivity to the server. Ping requests are disabled on the WildFire server. Best practice to test connectivity is to Telnet to the server on port 443. To verify, if any files have been forwarded to the server, use the following command: > show wildfire status Connection info: Wildfire cloud: default cloud Status: Idle Best server: va-s1.wildfire.paloaltonetworks.com Device registered: yes Service route IP address: 10.30.24.52 Signature verification: enable Server selection: enable Through a proxy: no Forwarding info: file size limit (MB): 2 file idle time out (second): 90 total file forwarded: 0 forwarding rate (per minute): 0 concurrent files: 0 The total file forwarded counter will provide the number of files being forwarded to the server. Thanks
... View more