In the Nebula console, on the Endpoints page under the Status column, a Status indicator error message means there is an issue on the endpoint. Click on the indicator to display the error message.
Error messages
Error/Description | Resolution |
|
To resolve this issue, see Endpoint didn't start correctly in Endpoint Detection and Response. |
|
To resolve this issue, see Server Rollback Location is invalid using Endpoint Detection and Response. |
|
To resolve this issue, see Mac endpoint missing Full Disk Access in Nebula. |
|
To resolve this issue, see Windows 2019-09 Security Update for Windows devices running business products. |
|
To resolve this issue, see Nebula endpoint software update May 5, 2022. |
|
To resolve this issue, see Turn on Base Filtering Engine for your Nebula endpoints. |
|
To resolve this issue, see Kernel module not running in Endpoint Detection and Response. |
|
To resolve this issue, see System requirements for Nebula. |
|
To resolve this issue, install .NET version 4.6.2 or higher. For more information, see System requirements for Nebula. |
|
To resolve this issue, uninstall and reinstall the endpoint agent on the affected device. |
|
To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
To resolve this issue, restart the endpoint or contact Support. |
|
To resolve this issue, see Change Windows Firewall state with Group Policy Management Console. |
|
To resolve this issue, Collect Endpoint Agent diagnostic logs in Nebula and contact Support. |
|
To resolve this issue, use the minimum supported OS version Windows 10 or later. For more information, see Requirements for Firewall Management in Nebula. |
|
To resolve this issue, see Browser Phishing Protection installation failed - Nebula. |
|
To resolve this issue, add the configuration profile for the Browser Phishing Protection extension to your MDM. For more information, see Browser Phishing Protection MDM Deployment - Nebula. |