Skip to content

Troubleshooting

ChristianHandy edited this page Nov 17, 2026 · 2 revisions

Troubleshooting

Lost the admin password

FleetPilot stores only a hash, so the password can't be read back.

  • Proxmox container: the first password is in the container (run on the Proxmox node):
    pct exec <CTID> -- cat /root/fleetpilot-credentials.txt
  • Anywhere (also when that file is missing): set a new one on the FleetPilot machine. In a Proxmox container, prefix it with pct exec <CTID> -- and leave out sudo.
    sudo bash /opt/fleetpilot/reset-password.sh --generate
    --generate prints a random password, without it you type one, --list lists the users. Two-factor sign-in stays as it is; open sessions are signed out.

Common problems

Problem What to do
The page does not load systemctl status fleetpilot nginx, then journalctl -u fleetpilot -n 50
http://<ip> does not answer Use https://<ip>. Port 80 is left free on purpose
Certificate warning Expected with the self-signed certificate. Accept it once or install your own
"Security token expired or missing" The page was open too long or cookies are blocked: reload. Behind your own proxy, pass X-Forwarded-Proto: https
Locked out after failed sign-ins Wait 10 minutes (set in Security center → Sign-in rules) or reset the password (above)
A server shows offline FleetPilot checks the SSH port. Check address, port and firewall, then test: sudo -u fleetpilot ssh -i /opt/fleetpilot/.ssh/id_ed25519 user@server
"Host key changed" The server was reinstalled or its address moved. If expected, remove its line from /opt/fleetpilot/data/known_hosts
Linux updates never finish The SSH user probably needs a sudo password. Give it a passwordless sudo rule for the package manager (#210)
Windows host can't be reached Enable the OpenSSH server feature and use an administrator account (Windows support)
Installer stops in a Proxmox container Run the Proxmox update command again; it resumes. Log: journalctl -u fleetpilot
Plugin folder is read-only Intended. Copy the plugin into /opt/fleetpilot/addons as root and restart FleetPilot

Still stuck?

Open an issue with your FleetPilot version and the output of journalctl -u fleetpilot -n 100 (remove addresses and names you consider private), or ask in Discussions. Security problems go to private reporting.

Clone this wiki locally