Install your first probe
Create a Scout probe in RECON, save its API key, run the install command on the Linux machine and check that the probe shows as Online.
- Updated October 12, 2026
- Verified on RECON v3.3.0
- 3 min read
- Watch 2:17
Goal
Install a single Scout probe on one network, from creating it in RECON to seeing it Online and ready for its first internal scan. In the video the probe is called magazzino-chiari and covers the Meccanica Adda warehouse network.
Video chapters
Prerequisites
- A 64-bit (x86_64 or ARM64) Linux machine with systemd, dedicated to the probe and connected to the network to analyse.
- Root or sudo access on the machine.
- Outbound HTTPS on port 443 to
recon.orizon.one. - A RECON account with access to internal scans.
- A password manager to store the probe's API key.
Steps
Open the install wizard
In the sidebar, open Internal Probes and click Add probe. Keep the Deploy New Probe tab selected.
Choose the company
In the Company step, select Meccanica Adda from your saved companies, or look up a new one. In the Company Data step the details are already filled in: click Continue.
Name the probe and pick the platform
In the Probe step, enter a name that says where the probe sits, for example
magazzino-chiari: lowercase letters, digits and hyphens, 3 to 48 characters. If you leave it blank, RECON derives it from the company name. Under Platform, chooseLinux x86_64 (amd64)orLinux ARM64, then click Create probe and generate key.Save the API key
In the API Key step, RECON shows the key only once. Store it in your password manager, tick I have saved this API key securely and click Continue.
Copy the install command
In the Install step, click Copy command. The command contains this probe's credentials and a single-use install token that is valid for 24 hours: always copy it, never retype it.
Run the command on the machine
On the Linux machine, paste the command and run it as root or with
sudo. When the installer asks, pick your language (English, Italiano or Espanol). The installer checks the machine, downloads the probe software, registers the probe with RECON and installs it as a systemd service that starts at boot.Confirm in RECON
Back in RECON, click I've run the install command. The wizard shows "Waiting for probe to check in...": once the probe starts, it sends its first heartbeat within 30 seconds.
Finish networks, Active Directory and Done
After the first heartbeat, choose the networks to scan in the Networks step and click Save configuration. The AD Credentials step is optional: you can skip it with Skip this step. In the Done step the probe is ready and you can click Launch first scan.
Result
On the Internal Probes page the new probe shows as Online. If you installed it on its own, it is a single probe outside any group.
On the machine you can check the service status and the connection to RECON:
sudo scout dashboardFor a quick check without the interactive view, use sudo scout status instead.
Troubleshooting
- The installer says the install token has expired or was already used. The token is valid for 24 hours and works only once. On Internal Probes, open the probe's menu, choose Re-issue install command and run the new command.
- The wizard keeps waiting for the first heartbeat. After 5 minutes RECON shows "Haven't connected yet?" with commands to run on the machine:
sudo systemctl status scoutandjournalctl -u scout -n 50. Also check that the machine can reachrecon.orizon.oneover HTTPS. - You lost the API key. The key is shown only once: if you lose it, you have to rotate it. From the probe's menu, choose Rotate API key.
- The installer does not start. It needs Linux, systemd and root: see the guide on preparing the machine.