Skip to content

Troubleshooting

Install and decoys

Symptom Cause and fix
The installer allows fewer decoys than you want One decoy per usable interface and at most 3 in total. Add network cards (then add-decoy) or remote sensors.
"ReD-Pot Community Edition supports up to 3 decoys in total ..." All slots are used. Remove a local decoy (sudo ./install.sh remove-decoy NAME), revoke a remote sensor, or cancel a pending join in Deception. Revoking a local decoy does not free its slot. After a --force reinstall, remote sensors of the old install still count until you revoke them.
add-decoy: "the ReD-Pot console is not running" The decoy count is read from the running manager. Run sudo systemctl start redpot, then add-decoy again.
"already contains an installation" when adding a decoy Use sudo ./install.sh add-decoy. A reinstall (--force) creates a new persona and baits.
An interface is missing from the list It is shown under Not usable with the reason (down, no cable, no IPv4, unusual name). Fix it and run the installer again.
A decoy needs a port that a host service uses The installer names the service and offers to stop and disable it (re-enabled by uninstall), or lets you choose another interface or other roles.
A service on the server stopped answering after the install It listens on an interface that now holds a decoy (the management interface included, if a decoy shares it). Only the decoy's ports and the admin ports answer there. Reach the service through another interface, or move the decoy.
"another ReD-Pot installer is already running" Only one installer at a time. Wait for the other one (another SSH session or tmux) to finish.
apt errors during install The installer repairs interrupted dpkg runs and ignores broken third-party repositories. If it still fails, run sudo apt-get -f install and start again.
apt says files list file for package ... is missing final newline The package database was damaged by a power cut. The installer detects this and offers to rebuild the damaged lists.
"this install was made by an older ReD-Pot" Installs before 1.0.0 cannot be updated in place: uninstall, then install again. 1.0.0 to 1.0.1: sudo ./install.sh update.

Access

Symptom Cause and fix
The web UI does not open Your address is not in the web UI allow-list, or you use an address that is not on the management interface. Check Admin access in INSTALL-INFO.txt; change the list with sudo ./install.sh set-access from an SSH session on the manager.
Lost SSH after a 1-interface install SSH moved to the port shown in the summary and in the login banner: ssh -p <port> user@server.
SSH did not move / "sshd -t: Missing privilege separation directory" Ubuntu 22.10+ starts sshd on demand (ssh.socket), so /run/sshd may not exist yet; the installer creates it. It also comments out extra Port 22 lines in /etc/ssh/sshd_config.d/*.conf (restored on uninstall) and switches the fixed-port ssh.socket of 22.04 to ssh.service. It stops with a clear message if ListenAddress contains a port.
Lost the admin token or ports sudo cat /opt/redpot/manager/INSTALL-INFO.txt. The live token is console.admin_token in /opt/redpot/manager/rpot.json. New token: sudo ./install.sh reset-token.

Remote sensors

Symptom Cause and fix
Sensor: "presents a different certificate" The join string belongs to another manager, or the manager was reinstalled. Create a new join command on the right manager.
Sensor: "enrollment refused: decoy limit reached" The manager has no free slot. Free one and create a new join command.
A remote sensor is offline after a reboot (L4 "stopped reporting") Its address changed (DHCP) and the manager's sensor-API allow-list refuses the new one. On the manager: sudo ./install.sh set-access --yes --allow-sensor <new address or subnet>. Better: a static address or a DHCP reservation.
A sensor shows "offline" The red banner shows since when. Check systemctl status redpot-sensor on the sensor and the route to the manager's sensor API port. Events from the outage stay in the sensor's local log and are not sent later.

Console

Symptom Cause and fix
The world attack map is empty It shows only attackers with public IPs. Decoys on internal addresses only see internal attackers; those are on the Overview map. No GeoIP yet? sudo ./install.sh geoip.
Clock warning banner The manager's clock and the browser's differ by more than 2 minutes, or the manager's clock is not NTP-synchronised. Fix NTP on the manager.
Bait document opened but no alert The opening host is not in the web UI allow-list. See Access allow-lists.

Where to look

systemctl status redpot                 # manager service (sensor: redpot-sensor)
sudo docker ps                          # containers
sudo docker logs redpot-console-1       # manager log
sudo docker logs redpot-fs01-1          # a decoy (lower-case host name)

Still stuck? See Support.