Just Published! Threat Report: Exposing Malware in Linux-Based Multi-Cloud Environments | Download Now

WildFire local appliance test fails with "Unable to connect to appliance: WildFire not accessible."

WildFire local appliance test fails with "Unable to connect to appliance: WildFire not accessible."

Version

7.2.1 - WildFire local appliance is not supported in earlier releases.

Topic

When trying to add a local WildFire appliance as a bit9 connector, you get the message "Unable to connect to appliance: WildFire not accessible."

Possible Workaround

Testing of Wildfire local appliance might show "Wildfire not accessible", but appliance still works. This will be resolved in the next patch. Workaround is to just save the settings and use the local Wildfire appliance (without testing).

Additional Troubleshooting

Confirm there are no firewalls or proxy between the Bit9 console and the WildFire appliance.

From the Bit9 machine, open a web browser and go to the Wildfire URL to test connectivity.

What are the results when you try to ping the WF appliance from the Bit9 Server?

What are the results when you run a trace route from the Bit9 server to the WF appliance?

Next Steps

If the above information did not resolve the issue, then please provide the following information to support.

What is the exact build of 7.2.1 you are running?

What is the exact version/build of the WildFire appliance?

Do you have a way to validate the key on your WildFire appliance in some other way (outside of Bit9 console)?

Collect the following data from the Bit9 console:

1. Log in to the Bit9 console

2. Browse to https://<Bit9 server name>/support.php and go to the Diagnostics tab

3. Set the following logging:

a. Logging Duration: 30 Minutes

b. Sampling Interval: 30 Minutes (default)

c. Debug Level: High

d. Reporter Log Level: High

e. Script Debug Level: High

4. Click Start Logging

5. Open Bit9 configuration page on PAN tab. Enter a new local appliance for File Analysis as <IP Address>

6. Save this setting and enable the file analysis (do not care about Test button). Take a screenshot of this page after being saved.

7. Find a file in the file catalog and analyze the file with Wildfire.

8. Send the screenshot of Requested files page to see if the files are sent to Wildfire.

9. After 30 minutes, go back to https://<Bit9 server name>/support.php and go to the Diagnostics tab click on “View available log files” and download the files we just created.

10. Send debug logs and screenshot to Bit9 support.

If the data is too large to attach to your open case then please upload at Cb Vault .

Labels (1)
Was this article helpful? Yes No
No ratings
Article Information
Author:
Creation Date:
‎08-28-2015
Views:
479
Contributors