devlanes debug why UNIT explains a unit that is not running or not ready, and devlanes doctor checks the machine. Text in capitals, such as UNIT, stands for the name devlanes prints there.
| What you see | Cause | Fix |
|---|
UNIT couldn't start: PROGRAM: command not found on PATH | The program is not on the PATH of the shell that started the lane | Start the lane from a shell that finds it (Bring lanes back after a reboot) |
UNIT wasn't ready in time | The ready check never passed | Wait until a service is ready |
nothing accepts connections on port PORT | The service listens on another port than the one devlanes gave it | Give a service several ports and hostnames |
A service crashed, and status still shows it ready | A watcher such as node --watch keeps the process alive | Read devlanes logs for the service and run devlanes restart on it (When a service fails) |
port PORT is taken by pid N | Another program holds a port of the lane | Stop that program, then start again |
PATH has no value in LANE | An expression such as ${{ env.API_KEY }} has no value, often a missing .env | Read .env values and pin tool versions |
global_env.NAME has no value in LANE on each service, under a profile with infra: false | The value reads a container the profile did not start | Share settings and choose which services start |
Docker isn't running or can't be reached | The project has containers and Docker is down | Start Docker |
| What you see | Cause | Fix |
|---|
Lanes are idle with needs start from a shell | The daemon restarted, or ended with the terminal | Bring lanes back after a reboot |
| The daemon stops when you close a terminal on Windows | That terminal ends the processes it started | Windows |
devlanes: command not found in a project whose package.json lists devlanes | The project pins devlanes, so the command is not on your PATH | Run it as npx devlanes (Install devlanes) |
no devlanes.yaml in DIR or its parents | The command ran outside a project | Add devlanes to a project |
the running daemon is devlanes VERSION ... and cannot serve this CLI | The daemon runs another release than the CLI | devlanes daemon restart (Update and uninstall) |
the port pool has no free block of N ports for another lane | Old lanes hold every port block | Remove lanes |
auto-spawn refused in sandbox | The command runs inside an agent’s sandbox | Use devlanes from an agent sandbox |
| What you see | Cause | Fix |
|---|
needs_auth in devlanes remote ls | Reconnecting needs your SSH password, passphrase or host key | devlanes remote connect BOX in a terminal |
needs_pairing in devlanes remote ls | The box no longer accepts this machine | Connect to a box |
Other states and warnings of devlanes remote ls | | Remote connection states |