Cyberlop supports HTTPS repository addresses only, so an SSH address that starts with git@ will not work. Copy the HTTPS clone address from your code host, enter it in Repo URL (HTTPS), and add a Git token if the repository is private.
Why this happens
The field is labelled Repo URL (HTTPS), and its help text says "Public repos cloned at scan launch; SSH git@ not supported." An address like git@host:acme/web.git uses SSH, so it does not fit. SSH is not supported for cloning, whether the repository is public or private.
How to fix it
- On your code host, open the repository and choose the HTTPS option in its clone menu.
- Paste that address somewhere safe. It starts with
https://, for examplehttps://git.example.com/acme/web. - In Cyberlop, go to Targets and click + New target.
- Choose White-box and paste the address into Repo URL (HTTPS).
- For a private repository, save a read-only token first under Settings → Git Access.
- Click Create target.
If you already saved the target with the wrong address, you cannot edit it. Targets are immutable, so delete it and create it again, remembering that deleting also removes its profiles, scans and findings.
Still not working?
- Check that the address is complete and has no stray spaces at the start or the end, which is easy to miss when you paste.
- Confirm that the repository is public, or that a token is saved and the host is in Allowed hosts.
- Make sure the scan type is White-box, since black-box targets ignore the repository.
Read what a private repository needs for token details. We can help at /contact.
Related questions
- How do I connect a Git repository to a target?
- How do I scan a private repository?
- My private repository won't clone. What do I need?
- The New target dialog says a repo URL is required, but my app has no repository. What do I do?
- How do I change a target's URL or repository after creating it?
Connect a repository to Cyberlop for white-box scans
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.