Willow bootloops as it cannot connect to WAS

[kevdliu]

Decided to try out the fancy new WAS today but I'm having trouble getting willow to boot after flashing the image generated by WAS. I pulled the below logs from the willow console:

ESP-ROM:esp32s3-20210327

I (436) esp_image: segment 4: paddr=001dc234 vaddr=4037beW (00:00:08.239) PERIPH_WIFI: Wi-Fi disconnected from SSID N24, auto-reconnect enabled, reconnect after 1000 ms

W (00:00:11.643) PERIPH_WIFI: Wi-Fi disconnected from SSID N24, auto-reconnect enabled, reconnect after 1000 ms

W (00:00:13.158) PERIPH_WIFI: WiFi Event cb, Unhandle event_base:WIFI_EVENT, event_id:4

I (00:00:14.159) WILLOW/WAS: initializing WebSocket client (ws://192.168.1.230:8502/ws)

I (00:00:14.160) WILLOW/WAS: initializing WebSocket client (ws://192.168.1.230:8502/ws)

E (00:00:16.165) WEBSOCKET_CLIENT: Could not lock ws-client within 2000 timeout

E (00:00:16.165) WILLOW/WAS: failed to send WAS get_config message

E (00:00:24.167) esp-tls: [sock=54] select() timeout

E (00:00:24.167) TRANSPORT_BASE: Failed to open a new connection: 32774

E (00:00:24.169) TRANSPORT_WS: Error connecting to host 192.168.1.230:8502

E (00:00:24.176) WEBSOCKET_CLIENT: Error transport connect

I (00:00:24.183) WILLOW/WAS: WebSocket disconnected

E (00:00:44.189) esp-tls: [sock=54] select() timeout

E (00:00:44.190) TRANSPORT_BASE: Failed to open a new connection: 32774

E (00:00:44.191) TRANSPORT_WS: Error connecting to host 192.168.1.230:8502

E (00:00:44.198) WEBSOCKET_CLIENT: Error transport connect

I (00:00:44.205) WILLOW/WAS: WebSocket disconnected

E (00:01:04.211) esp-tls: [sock=54] select() timeout

E (00:01:04.211) TRANSPORT_BASE: Failed to open a new connection: 32774

E (00:01:04.213) TRANSPORT_WS: Error connecting to host 192.168.1.230:8502

E (00:01:04.221) WEBSOCKET_CLIENT: Error transport connect

So it looks it's failing to connect to WAS? I was able to connect to the WAS websocket using Postman with the same ws://192.168.1.230:8502/ws address so I'm not sure why Willow is failing to.

[kevdliu]

Wait it might be a firewall issue on my end. I'll double check and report back.

[kevdliu]

OK I fixed the firewall issue but still seeing the same errors. I was able to open a websocket connection to WAS from another computer on my LAN should it shouldn't be the firewall blocking it anymore.

[kevdliu]

Final update: It ended up still being an issue with my firewall. I wasn't sure which executable specifically was being blocked so I just added a rule to allow all traffic through port 8502. Works great now!