this page is outdated but may help you

A guide to common issues and their solutions for GhostESP firmware.

• Flashing Problems
• Board-Specific Issues
• WiFi & Connection Issues
• Display & UI Problems
• Evil Portal Issues
• Dual ESP32 Communication Issues
• Getting Help

• Problem: Can't connect or flash fails
• Solutions:
  1. USB Preparation:
     • Use data-capable USB cable (not charge-only)
     • Try different USB ports
     • Clean USB connections
  2. Driver Issues:
     • Install correct USB drivers
     • Clear browser cache for web flasher
     • Try different browser if issues persist

• Basic Method:
  1. Hold BOOT button
  2. Connect USB
  3. Release BOOT after connection
• Alternative Method (if basic fails):
  1. Hold BOOT
  2. Press RESET while holding BOOT
  3. Release RESET
  4. Release BOOT

• Wrong Board Selected
  • Verify physical USB port type
  • Match board selection to actual hardware
  • Check if board has multiple ports
• Connection Timeout
  • Retry bootloader sequence
  • Try different USB cable
  • Verify power LED is on

• Port Configuration:
  • White port (WROOM): GUI/display firmware only
  • Orange port (S2): No BLE support
• Common Problems:
  • Cross-flashing between ports causes issues
  • Communication errors between Flipper and board
• Solutions:
  1. Flash correct firmware to each port
  2. Don't mix firmware between ports
  3. If port stops responding:
     • Enter bootloader mode
     • Reflash correct firmware
     • Verify connections

• All Models Now Supported:
  • Single USB-C
  • Dual USB ports
  • MicroUSB variants
  • AITRIP CYD (ESP32-2432S028R)
• Flash Requirements:
  • Use bootloader mode sequence
  • Select correct board in flasher
  • Clear cache if connection fails

• Problem: Can't connect to the GhostNet ap

• Solution:

  1. Try the default password: GhostNet

  2. Try the credentials you use to login to the web interface.

     • The GhostEsp used the same credentials for the web UI as it does for the wifi access point

• Problem: Can't access web interface

• Solution:

  1. Connect to ESP's WiFi network
  2. Browse to 192.168.4.1
  3. Enter WiFi credentials in settings

• Problem: I get booted from the GhostNet AP every time I issue a wifi command

• Solution:

  • This is a limitation of the ESP32. The chip can only serve an AP or connect/monitor other networks
  • Wait until the command finished and reconnect to the AP, or use a different control interface such as serial, the flipper app, or a touch screen.

• Design Layout:
  • Upper screen half: Move UP
  • Lower screen half: Move DOWN
  • Middle: SELECT
  • Main menu: Direct touch selection

• Black Screen:
  • Verify correct firmware for display
  • Check power connections
  • Try reflashing firmware
• Garbled Display:
  • Update to latest firmware
  • Check display cable connection
  • Verify board selection matches hardware

• Problem: Display turns off too quickly
• Solution:
  • Adjust display timeout in settings
  • Use "Never" setting to keep display always on
  • Power saving mode can be disabled if needed

1. Configure portal settings in web UI
2. Verify ESP has IP address before starting
3. Use appropriate URLs:
   • Desktop: domain.local/login
   • Mobile: include "https://" in portal URL
4. Note: If redirecting to MSN, you're likely connected to actual internet instead of the ESP portal

If you're using the Evil Portal feature, note the following:

1. Connect to the Evil Portal AP: Instead of connecting to "GhostNet," connect to the Evil Portal's Access Point (AP). The portal AP's password is configurable and is not automatically the same as the SSID; by default the portal AP may be open (empty password). Use startportal <file> <AP_SSID> [PSK] to set a PSK.
2. Web UI Replacement: When the Evil Portal is active, the normal web UI is replaced. You won't have access to the web UI until the board is restarted.
3. Refreshing Access Points: If "GhostNet" still appears after activating the Evil Portal, turn your device off and on again.

Tip: Windows and other devices sometimes cache network access points, so refreshing your Wi-Fi can help display the correct AP.

• Desktop Issues:
  • Auto-redirect to MSN: ESP using actual internet DNS instead of portal
  • Failed to fetch: Check portal configuration
• Mobile Issues:
  • "Header fields too long": Add "https://" to URL
  • CSS display issues: Known limitation on mobile

• Problem: HTML upload fails
• Solution:
  • Ensure HTML is under 2048 bytes
  • Use simple HTML without complex CSS/JS
  • Try the built-in template first

• Problem: Devices not connecting
• Solutions:
  1. Check wiring (TX→RX, RX→TX, GND connected)
  2. Ensure both devices are powered
  3. Reboot both devices simultaneously
  4. Wait 30 seconds for discovery
  5. Run commstatus to check connection

• Problem: Commands not working on remote device
• Solutions:
  1. Verify connection with commstatus
  2. Use exact GhostESP command syntax
  3. Check if remote device is responsive
  4. Try reconnecting with commdisconnect then reboot

1. Check latest firmware version
2. Review troubleshooting steps
3. Gather information:
   • Board type and ports
   • Firmware version
   • Error messages
   • Steps to reproduce

• Use support form template
• Check apps_data/ghostesp for logs
• Review serial terminal output
• Command help: help