Offline means the agent has stopped sending its regular signals to Cyberlop. The container may have stopped, the machine may be off, or the outbound HTTPS route may be cut. Restart the container, check the network, then reload.
Why this happens
The agent stopped checking in. A healthy agent sends regular signals to Cyberlop, called heartbeats. Once they stop, the row changes to offline. Someone may have shut the agent down, the machine may be off, or something may block the route to Cyberlop.
How to fix it
- Open Settings → Scan Agents and read Last seen for the agent.
- On the agent's machine, check that the container is still running.
- Start the container again if it has stopped.
- Check the machine has outbound HTTPS to
app.cyberlop.comon port 443, and that no proxy or firewall change has cut it off. - Reload the page. The status should return to online once the agent checks in.
Last seen helps you work out when the trouble began. Compare it with changes on that machine around the same time, such as a restart, an update or a network change.
Still not working?
A scan sent to an offline agent cannot run, so fix the agent before you start more scans on its profiles. If you cannot recover it, remove the agent in the same table. Its profiles go back to the Cyberlop cloud, which cannot reach internal apps, so set up a new agent and choose it as the Scan location again.
Read more: what the statuses mean, how to remove an agent and what Last seen shows. Need help? Use the contact page.
Related questions
- What do pending, online and offline mean for a scan agent?
- How do I see when my scan agent last checked in?
- How do I see whether my scan agent is online?
- How do I remove a scan agent?
- What network access does a scan agent need?
Cyberlop self-hosted scan agents: scan private apps from inside your network
Step-by-step, with annotated screenshots.
Updated · Back to the help centre
Error still showing?
Send us the exact message and the page you were on. We will reply with the fix.