If an endpoint is not displaying on the endpoints page of the Nebula console, this indicates one of the following:
- Installation was not successful and the Malwarebytes Endpoint Agent did not start.
- The endpoint has been deleted, in which case the Event log should be reviewed.
- Communication of the Malwarebytes Endpoint Agent is being blocked.
- The Malwarebytes Endpoint Agent has started and is communicating, but registration has failed.
Unsuccessful installation may be due to missing network access requirements, outdated Windows certificates, or the Mac installation file was modified.
Symptoms
Cannot find endpoint in Nebula console.
Environments
- Malwarebytes Nebula
Windows, Mac, and Linux
Cause: Endpoints running the endpoint agent require our network access domains to connect with Nebula.
Resolution:
- Update your firewall with our network access requirements to validate communication with Malwarebytes Nebula. For more information, see Network access requirements and firewall settings for Malwarebytes Nebula.
- For Windows, test the connection with the endpoint Agent command line tool. For more information, see Use the Endpoint Agent Command-line tool with Malwarebytes Nebula.
- For Linux, test the connection with command line. For more information, see Commands for Malwarebytes Nebula Linux endpoints.
Windows only
Cause: Windows endpoints require certificates to connect with Nebula.
Resolution: Check and update the endpoint certificates. For more information, see Endpoint certificates are outdated in Malwarebytes Nebula.
Mac only
Cause: Mac endpoints must use an unmodified .pkg file to install and connect.
Resolution: Verify the installation file wasn't renamed. For more information, see Add Mac endpoints in Malwarebytes Nebula.