Title: Connect to GhostESP
Description: Choose the best way to control your GhostESP device
URL: /latest/getting-started/control-methods/
Version: latest
Section: Getting Started
Search index: /search-index.json

# Connect to GhostESP

> Choose the best way to control your GhostESP device

## On this page

- [Choose a control method](#choose-a-control-method)
- [Connect](#connect)
- [Troubleshooting](#troubleshooting)
- [Related tasks](#related-tasks)

---

Once GhostESP is flashed and has completed its first boot, control it from the device itself, a browser, a serial terminal, a Flipper Zero, or the desktop Control App. Start with the on-device UI or serial CLI if you are unsure which interface you want.
## Choose a control method
Method |
Best for |
What you need |
Important limitation |
On-device UI |
Quick local use on supported display boards |
A board with a display and supported input |
Available menus depend on the board hardware. |
WebUI |
Settings, files, and terminal access from a phone or computer |
Connect to GhostNet, then open ghostesp.local or 192.168.4.1 |
The device cannot host its access point while using Wi-Fi or BLE locally. |
Serial CLI |
Full command access and diagnostics |
USB data cable and a serial terminal at 115200 baud |
Requires a wired connection. |
Flipper Zero App |
Portable control through a compatible Flipper setup |
GhostESP Flipper app and wiring |
Feature availability depends on the connected board. |
Desktop Control App |
Serial workflows and advanced customization |
USB data cable and the desktop app |
Requires a computer. |
## Connect
On a supported display board, open the main menu and choose the feature you want, such as Wi-Fi → Scanning, then follow the on-screen prompts with the board’s supported touch, keys, or encoder controls. Over a wired link, connect the board with a USB data cable and open a serial console at 115200 baud, then send help and confirm GhostESP prints a command list.
## Troubleshooting
- GhostNet is missing: Restart the board and confirm that flashing completed successfully.
- The WebUI does not open: Use 192.168.4.1 if ghostesp.local does not resolve.
- The serial terminal is blank: Send help; GhostESP can be quiet until a command runs. Confirm the port and 115200 baud rate.
- A Wi-Fi or BLE command disconnects the WebUI: This is expected on a single board. Use the on-device UI, serial CLI, or [GhostLink](/latest/getting-started/dual-communication/) for those radio tasks.
## Related tasks
- [WebUI guide](/latest/getting-started/webui-guide/)
- [CLI reference](/latest/getting-started/command-line-reference/)
- [Control App](/latest/companion-tools/control-app/)
- [Try your first scan](/latest/getting-started/first-scan/)