Troubleshooting
OpenHands only supports Windows via WSL. Please be sure to run all commands inside your WSL terminal.
Launch docker client failed
Description
When running OpenHands, the following error is seen:
Resolution
Try these in order:
- Confirm
docker
is running on your system. You should be able to rundocker ps
in the terminal successfully. - If using Docker Desktop, ensure
Settings > Advanced > Allow the default Docker socket to be used
is enabled. - Depending on your configuration you may need
Settings > Resources > Network > Enable host networking
enabled in Docker Desktop. - Reinstall Docker Desktop.
Permission Error
Description
On initial prompt, an error is seen with Permission Denied
or PermissionError
.
Resolution
- Check if the
~/.openhands-state
is owned byroot
. If so, you can:- Change the directory’s ownership:
sudo chown <user>:<user> ~/.openhands-state
. - or update permissions on the directory:
sudo chmod 777 ~/.openhands-state
- or delete it if you don’t need previous data. OpenHands will recreate it. You’ll need to re-enter LLM settings.
- Change the directory’s ownership:
- If mounting a local directory, ensure your
WORKSPACE_BASE
has the necessary permissions for the user running OpenHands.
Unable to access VS Code tab via local IP
Description
When accessing OpenHands through a non-localhost URL (such as a LAN IP address), the VS Code tab shows a “Forbidden” error, while other parts of the UI work fine.
Resolution
This happens because VS Code runs on a random high port that may not be exposed or accessible from other machines. To fix this:
- Set a specific port for VS Code using the
SANDBOX_VSCODE_PORT
environment variable: - Make sure to expose the same port with
-p 41234:41234
in your Docker command. - If running with the development workflow, you can set this in your
config.toml
file: