Platform

Platform overview How it works Authorization testing Evidence & reports Private scanning Integrations

Solutions

Security agencies Product teams Regulated industries Partner programme

Learn

Blog Knowledge hub Compare

Resources

Pricing Documentation Help centre FAQ Security & data What we haven’t proved

Company

About Contact Careers Sign in to the platform Start a $199 pilot →

Home / Help centre / Troubleshooting

Troubleshooting

Why is my scan agent stuck on pending?

Quick answer

The agent has not enrolled yet. Start the container command on a machine inside your network, make sure it has Docker and outbound HTTPS on port 443 to app.cyberlop.com, then reload. If the token is gone, add a new agent.

Why this happens

This agent exists in Cyberlop but has not enrolled. Adding one only creates the record and a one-time enrollment token. Nothing is live until the container runs on your side, trades that token for a lasting key and begins checking in for work over outbound HTTPS. Until then the row says pending, and no scan can reach it.

How to fix it

  1. Open Settings → Scan Agents and confirm the agent is still listed.
  2. Run the ready-made container command on a machine inside your network. The machine needs Docker.
  3. Check the machine has outbound HTTPS to app.cyberlop.com on port 443, and ask your network team whether a proxy or firewall rule stands in the way. This is a common blocker.
  4. Wait a short while, then reload the page. The status should change to online. Still pending? Then the machine most likely cannot reach Cyberlop yet.
  5. Lost the command or its token? Add a new agent and use the new command.

Cyberlop shows the token and command once only, so you cannot read them again later. A new agent gives you a fresh pair. Copy it before you leave the page.

Still not working?

Look at the container's own output on that machine for connection errors. Confirm the machine reaches the internet. Check that nothing on the route rewrites or inspects HTTPS traffic in a way that breaks the connection to Cyberlop. Make sure you ran the command for this agent. An older one will not do.

Related: running the agent container, network access an agent needs and a lost enrollment token. Still pending? Contact us on the contact page.

Full tutorial

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.