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 message | Description | Resolution |
|---|---|---|
|
|
This needs your immediate attention, as files cannot be cleaned and no events can be logged. | To resolve this issue, see Endpoint didn't start correctly in Endpoint Detection and Response. |
|
|
The backup path specified for this server either does not exist or is not available. Please check the specified backup path is valid. | To resolve this issue, see Server Rollback Location is invalid using Endpoint Detection and Response. |
|
|
Your team has not yet granted this endpoint permission to allow full disk access (FDA). For the best protection, we highly recommend that you grant this endpoint access to this capability. | To resolve this issue, see Mac endpoint missing Full Disk Access in Nebula. |
|
|
A missing Windows security update is required to update to the latest version. Protection updates will continue, but we cannot provide software updates without SHA-2 support. | To resolve this issue, see Windows 2019-09 Security Update for Windows devices running business products. |
|
|
An update is required to continue to receive product updates. Protection updates will continue, but you will be unable to utilize new products and features. | To resolve this issue, see Nebula endpoint software update May 5, 2022. |
|
|
Endpoint is not configured properly or has a problem. | To resolve this issue, see Turn on Base Filtering Engine for your Nebula endpoints. |
|
|
Endpoint Detection and Response will not work on Linux until this is resolved. | To resolve this issue, see Kernel module not running in Endpoint Detection and Response. |
|
|
Endpoint Detection and Response must be installed on a supported operating system. | To resolve this issue, see System requirements for Nebula. |
|
|
Ensure your endpoint has .NET version 4.6.2 or higher to continue receiving product updates. Protection updates will continue, but you will be unable to utilize new products and features. | To resolve this issue, install .NET version 4.6.2 or higher. For more information, see System requirements for Nebula. |
|
|
Uninstall and reinstall the endpoint agent on the affected device. | To resolve this issue, uninstall and reinstall the endpoint agent on the affected device. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
Ad blocking is disabled in the ThreatDown Mobile Security app. | Enable Ad blocking in the ThreatDown Mobile Security app. |
|
|
Web Protection is disabled in the ThreatDown Mobile Security app. | Enable Web Protection in the ThreatDown Mobile Security app. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The endpoint is not configured properly or has a problem. Please restart the endpoint agent service on the affected device, or contact support. | To resolve this issue, restart the endpoint agent or the device. If the error persists, contact Support. |
|
|
The plugin does not operate while Windows Firewall is controlled by a Group Policy. Windows Firewall should be in <Not Configured> state in Group Policy Editor. | To resolve this issue, see Change Windows Firewall state with Group Policy Management Console. |
|
|
The plugin received one or multiple firewall rules which are considered invalid. Please review the plugin log file to find out which rules could not be created. | To resolve this issue, Collect Endpoint Agent diagnostic logs in Nebula and contact Support. |
|
|
The plugin does not support the current operating system. | To resolve this issue, use the minimum supported OS version Windows 10 or later. For more information, see Requirements for Firewall Management in Nebula. |
|
|
The Browser Phishing Protection web extension couldn't be installed. | To resolve this issue, see Browser Phishing Protection installation failed - Nebula. |
|
|
The Browser Phishing Protection web extension couldn’t be installed because this endpoint is managed by an MDM (Mobile Device Management) solution. | 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. |
|
|
Real time protection failed to initialize. Please review the log for details. | Real-time protection isn't supported on Windows Subsystem for Linux (WSL) or kernels lacking fanotify support. If you encounter this error outside these cases, contact Support. |