Proxy Services
Manage trusted internal HTTP services behind the Raspberry Pi HAProxy ingress. Every change is validated before reload; invalid configurations are rolled back automatically.
Status
HAProxy runtime
Not ready
sudo: /usr/local/lib/fleetpilot/proxy-apply: command not found
Ingress address
https://fleetpilot.home/
FleetPilot remains the default route. Managed routes are matched by their path prefix before FleetPilot.
Safety model
Only administrators can change routes. FleetPilot validates names, paths, hosts and ports; the root-owned helper renders and reloads HAProxy.
https://fleetpilot.home/. FleetPilot stays on the root path /. A route such as /immich sends only requests beginning with /immich to the backend you select. The backend receives that original path, so it must support running below /immich. Do not use FleetPilot's root path or reserved paths.Add a service in four safe steps
1. Choose a unique public path
Use a short path such as /immich, /paperless or /grafana. Users will open https://fleetpilot.home/your-path.
2. Enter the internal destination
Enter the server's LAN address and the port the application already listens on. Example: an app at 192.168.1.52:3000.
3. Select a health path
Use / if a normal page returns HTTP 200, or the application's own health endpoint such as /healthz.
4. FleetPilot applies safely
The route is validated, HAProxy is tested and reloaded. If validation or reload fails, FleetPilot restores the previous working routes.
Example: public path /paperless + backend 192.168.1.56 + port 8000 means users browse https://fleetpilot.home/paperless. If Paperless only works at /, configure its own reverse-proxy base path first; FleetPilot intentionally does not rewrite application paths.
Proxmox console routes
Proxmox cannot safely run under a path such as /pve01, because its interface requests root-relative resources and console WebSockets. FleetPilot therefore assigns each Proxmox host a dedicated TLS passthrough port. Proxmox retains its own login and certificate.
All named Proxmox hosts already have a dedicated route, or no host named pveNN is registered.
Unraid console route
Unraid also uses root-relative web resources, so FleetPilot publishes its existing HTTPS interface on the dedicated central TLS port 8200. Unraid keeps its own login and certificate.
The registered Unraid host already has its dedicated route, or no host named unraid is configured.
Add internal service route
Managed routes
No additional routes are configured. FleetPilot is currently the default ingress service.