I added a scan agent but still can't run more scans at once. Why?

Why this happens

An agent brings its own capacity, but only once it works. Adding it in Settings creates it in a pending state. It becomes online after you run the container and it enrols with its one-time token. An agent that stops sending heartbeats shows as offline. Only an enrolled, online agent raises the limit.

How to fix it

1. Open Settings → Scan Agents and read the agent status.
2. If it is pending, run the docker run command on a machine inside your network. It needs Docker and outbound HTTPS. The token shows once, so if you lost it, remove the agent and add a new one.
3. If it is offline, restart the container and check the machine can reach Cyberlop on outbound port 443.
4. Open the scan profile and set Scan location to your agent. Scans from that profile then run on your network.
5. Start the scans again.

Still not working?

• Your plan still sets your limits. See them in Settings → Plan & usage.
• Read how an agent adds scan capacity and what to do when an agent is stuck pending.
• The full set-up is in the scan agents tutorial.

Remember that an agent only raises the limit on the scans it can take, so one that is enrolled but never reached by your profiles will not change how many scans you see running together in the app.

Still stuck? Contact us with the agent name.

Related questions

• Does adding a scan agent let me run more scans at once?
• Why is my scan agent stuck on pending?
• Why does my scan agent show as offline?
• How do I see whether my scan agent is online?
• How do I make a profile run on a self-hosted scan agent instead of the cloud?

Full tutorial

Cyberlop self-hosted scan agents: scan private apps from inside your network

Step-by-step, with annotated screenshots.

Updated 8 October 2026 · Back to the help centre