webserver crashing?

[tobiasboyd]

I got everything to compile and upload, went into the Wifi Manager AP and set up the Wemos w/ my SSID/pass, but when I try to hit its IP, I can see the page render for just a second, and then I get a connection reset. From the commandline, that looks like

[21:29:37] tobyb:~ $ http 10.0.0.28
HTTP/1.1 200 OK
Content-Type: text/html

http: error: ChunkedEncodingError: ("Connection broken: ConnectionResetError(54, 'Connection reset by peer')", ConnectionResetError(54, 'Connection reset by peer'))

[Qrome]

Can you tell me what version of the Wemos you are using?

I have yet to see that issue with the Wemos D1 Mini.

What do you see in the Serial Monitor?

[tobiasboyd]

Mine is a D1 mini - I am expecting the LED display module tomorrow from AMZN, do you think the sketch is crashing because it isn't wired up yet? Not much in the Serial Monitor, right after it flashes I see

0x2d
csum 0x2d
v614f7c32
~ld

[Qrome]

I just loaded it on one of my testing Wemos D1 Mini here at my desk and was able to view the webpage and I do not see any errors in the Serial Monitor at all. It seems to act normal without the LED displays attached.

[Qrome]

@tobiasboyd -- you should see lots of stuff going on in the Serial Monitor -- are you seeing the normal log lines? Set it up for 115200.

[tobiasboyd]

Ah, changing the baud rate does indeed show me a lot of messages in the Serial Monitor. I did a full erase flash, configured wifi again, and now I can see this when I hit port 80:

Remote IP: 10.0.0.20
GET / HTTP/1.1
Portland
Clouds
few clouds
60.8
3:00 PM
Signal Strength (RSSI): 86%
Client disconnected

[tobiasboyd]

I hooked up the LED panel, and everything else does work fine - though trying to connect to the webserver is still quite unstable (some browsers work better than others - Safari is more likely to succeed than FF or Chrome). One plus is that since the settings are passed in the query string, it's pretty easy to change things even if the web client's interface won't load.

[Qrome]

I use Chrome and FF almost exclusively. I am not sure why you are having issues on that.

[Qrome]

@tobiasboyd -- can you try it from another computer or from a mobile device?

[tobiasboyd]

Safari (on macOS) is the only browser I have found that will (sometimes) work @Qrome - Chrome and FF on Android 8.1 are both just as cranky as desktop, and httpie is too. But the Wemos is driving the LEDs fine, and I don't need to change the settings, so I think it's not a huge problem (unless other people report it too).

[Qrome]

Ok, we will Monitor -- if anyone else experiences this, please share some details. Thanks.

[Qrome]

I was finally able to reproduce this. I updated all the latest ESP8266 libraries and boards and once I did that the web server stopped working. I have made changes to the web server portion (much better now). It is in the 1.1 branch if you would like to test it.

[Qrome]

Changes have been published in Master and 1.1 release. Closing this item.

[Qrome]

@tobiasboyd -- yet one more merge and things are looking really good. Master branch is now sitting at 1.2 -- if you don't mind testing out that one. Thanks!

[tobiasboyd]

@Qrome - yes, I flashed last night, and everything works perfectly now. Thanks!