WebUI ERR_EMPTY_RESPONSE after updating esp8266 from 0.15.1 to 0.15.2

[popy2k14]

What happened?

I am running 3x esp8266 with 0.15.1.
HA messaged me today that there is an update tpo 0.15.2.
Done the update to one device over HA (arduino OTA method) and now the WebUI doesnt work.
What i have tried:

• Device is pingable

• Hyperion can send udp led data from my machine to the device and it is displayed (so it's not completely dead)

• Different browsers (brave, chrome & edge) throw ERR_EMPTY_RESPONSE when accessing: http://

• curl http://<ip> log find attached

• Tried to reach /update/ without successs

• Flashed 0.15.2 with usb from install.wled.me -> it worked and ui was reachable

• Restored json 0.15.1 configuration backup -> webui not reachable anymore

• -> so i assume also the first update flash with HA worked (exact same issue as flashed + restored manually) and thre is an issue with configuration compatibility between 0.15.1 & 0.15.2 (at least for my configuration)

• Flashed 0.15.1 with usb from install.wled.me -> it worked and ui was reachable

• Restored json 0.15.1 configuration backup -> webui is reachable, so my assumption from above seems right

To Reproduce Bug

Update esp8266 from 0.15.1 to 0.15.2.

Expected Behavior

WebUI is working

Install Method

Binary from WLED.me

What version of WLED?

0.15.1 & 0.15.2

Which microcontroller/board are you seeing the problem on?

ESP8266

Relevant log/trace output

curl http://192.168.0.52 -vvv
16:59:19.342000 [0-x] == Info: [READ] client_reset, clear readers
16:59:19.346000 [0-0] == Info: [SETUP] added
16:59:19.349000 [0-0] == Info:   Trying 192.168.0.52:80...
16:59:19.352000 [0-0] == Info: [SETUP] Curl_conn_connect(block=0) -> 0, done=0
16:59:19.357000 [0-0] == Info: [SETUP] Curl_conn_connect(block=0) -> 0, done=1
16:59:19.361000 [0-0] == Info: Connected to 192.168.0.52 (192.168.0.52) port 80
16:59:19.365000 [0-0] == Info: using HTTP/1.x
16:59:19.367000 [0-0] => Send header, 76 bytes (0x4c)
0000: GET / HTTP/1.1
0010: Host: 192.168.0.52
0024: User-Agent: curl/8.14.1
003d: Accept: */*
004a:
16:59:19.375000 [0-0] == Info: Recv failure: Connection was aborted
16:59:19.379000 [0-0] == Info: [WRITE] [OUT] done
16:59:19.381000 [0-0] == Info: closing connection #0
curl: (56) Recv failure: Connection was aborted

Anything else?

Any hint's?

Code of Conduct

• I agree to follow this project's Code of Conduct

[DedeHai]

thanks for reporting this. can you post the config that causes the UI breakdown?

[softhack007]

now the WebUI doesnt work.

It might be related to the modified cache-control handling in 0.15.2 - if your browser still has "older" WLED WebUI data in its cache, communication with the new release may get into trouble until the browser cache was cleared.

If you are on Windows with edge, try pressing <ctrl>+<F5> to clear the browser cache.

If this won't help, we need the cfg.json and presets.json from your device to reproduce the problem. As your WebUI seems unresponsive atm, you can open http://<WLED_IP>/edit to download the files.

[popy2k14]

I have updated the OP, after downgrading/flashing 0.15.1 with USB and restoring my config WebUI is working.
So yes, it seems an config issue after upgrading to 0.15.2 (at least with my configuration).

Here is my configuration, for privacy reasons i have changed SSID & device id (last mac part, but that should not matter).
But there is nothing special in there.

Edit: See post #5136 (comment) for config files

@softhack007 i doubt it's an caching issue because i have opened edge, which i never used with wled before.
Also curl shows no correct http answer, so to me the issue seems an http server issue on WLED's side in 0.15.2 in cobination with my restored config above.

[softhack007]

@popy2k14 please also attach the cfg.json as it is on your device, without any pretty-printing. Its ok if you replace the SSID & device-ID and local IP with dummy values. But we need a file that can be loaded onto our WLED dev boards without first un-pretty-printing everything.

Edit: we also need the presets.json file from your device, even if its "nothing special".

[popy2k14]

Here are the two files just changed SSID & mac part:

wled_cfg_Wohnzimmer Monitor.json
wled_presets_Wohnzimmer Monitor.json

[netmindz]

Please also try disabling the "polling for changes" in the "system options for WLED" in home assistant

[DedeHai]

bug confirmed, something strange going on, the ESP does not even register a web request, at least nothing in debug output. will dissect commits and see if I can find the commit causing it.

[DedeHai]

it stops working with this commit:
a9f52a1

[DedeHai]

@willmmiles
all I am getting when opening / refreshing the UI is this:
[13646]*** Dropping client 3FFF6B94 (50912): 0, 0/21488
[13651]*** Dropping client 3FFF68CC (50913): 0, 0/21712

[popy2k14]

@DedeHai thx for confirming.

Can you please drop the release (at least esp8266)?

[netmindz]

it stops working with this commit: a9f52a1

Can you give a bit more detail? I'm hoping it's not just as simple as any request for the UI as we surely would have seen this during the 8266 test of 0_15_x ?

[netmindz]

All 8266 related builds removed for now

[netmindz]

It appears to be related to the use of GPIO pin 3 for LEDs.

More details to follow