ESP32 WiFi reason 15 and 204: handshake timeout
The ESP32 found the network and started the WPA handshake, but it did not complete. Espressif names two causes: a wrong password, and a signal too weak.
WIFI_REASON_4WAY_HANDSHAKE_TIMEOUT (15), WIFI_REASON_HANDSHAKE_TIMEOUT (204). Espressif's description: 4-way handshake timeout. Handshake timeout.
The two are the same failure: ESP-IDF reports 4-way handshake timeouts as 204 for legacy reasons, and passes 15 on when the access point sends it.
The usual causes
- A wrong password. Espressif's table of reason codes related to a wrong password starts with this one. With WPA2 the access point does not say "wrong password"; the handshake just never completes.
- A weak signal. It is also in Espressif's table of codes related to low RSSI: the handshake frames get lost. Print the RSSI from a scan: the weaker it is (around -80 dBm and below), the more likely this gets.
- A WPA3 or mixed-mode network with settings the station does not match, on some routers. Try setting
threshold.authmodeto WPA2 and see whether it changes.
Tell them apart
If it fails every time right after boot, start with the password. If it connects most of the time and fails at the edge of coverage, it is the signal. A device that connected for weeks and starts failing after a router change usually has a password or security mode that no longer matches.
Where you see the number
In ESP-IDF, the WIFI_EVENT_STA_DISCONNECTED event carries it: ((wifi_event_sta_disconnected_t *) event_data)->reason. In Arduino, the ARDUINO_EVENT_WIFI_STA_DISCONNECTED event has it in info.wifi_sta_disconnected.reason, and WiFi.disconnectReasonName() turns it into a name. Log it every time: the reason is what separates a wrong password from a weak signal.
When it happens at a customer's site
On your desk you see the reason in the log. On a device behind someone else's router you only hear that it "goes offline sometimes". Pinscope keeps the device's logs and its WiFi signal over time, so you can see which reason it disconnected with and whether the signal was dropping before it did. Free for three devices. Remote logging.
Related errors: WiFi reason 201: NO_AP_FOUND · WiFi reason 202: AUTH_FAIL · WiFi reason 200: BEACON_TIMEOUT · WiFi disconnect reasons. All ESP32 errors: the list. Reason codes and their meaning from Espressif's Wi-Fi Driver guide and esp_wifi_types.h.
More
- Remote access to an ESP32 without TLS: what it measured and what it costs
- Reaching an ESP32 web server from outside its network
- Updating ESP32 firmware over the internet, with rollback
- Guru Meditation Error: decoding the backtrace, and crashes from the field
- Remote logging: ESP_LOG without a serial cable
- Heap and stack monitoring in the field
- An ESP32 behind CGNAT, 4G or Starlink
- TLS memory usage on the ESP32, and how to reduce it
- Sharing an ESP32 sensor page with anyone, without port forwarding
- ArduinoOTA over the internet, with a rollback
- ESP32 remote access compared: port forwarding, ngrok, Cloudflare Tunnel, Tailscale
- esp_http_server slow? The 250 ms delay and the fix
- Before the first ESP32 ships: a field support checklist
- ESP32 exception decoder: a Guru Meditation backtrace to lines, in the browser