Back to ESP8266 community
An ESP8266 HTTPS request fails when the rest of the application is running, although it works in a small test sketch. What should be measured before reducing TLS buffers, and which security checks must remain enabled?
ESP8266 DISCUSSION
ESP8266 HTTPS runs out of heap: how can TLS memory be reduced safely?
3 replies
248 views
4 participants
Latest activity · 27 Sep 2026ESP8266 HTTPS runs out of heap: how can TLS memory be reduced safely?
Re: ESP8266 HTTPS runs out of heap: how can TLS memory be reduced safely?
#2Measure free heap and the largest available allocation around connection setup, the handshake and response processing. Total free memory alone can hide fragmentation. Avoid retaining unnecessary response bodies or large temporary strings, and check whether reconnecting repeatedly leaks application-owned objects.
Re: ESP8266 HTTPS runs out of heap: how can TLS memory be reduced safely?
#3BearSSL buffer choices interact with the server's record behavior. Maximum Fragment Length Negotiation helps only when the server supports the negotiation. Test the actual endpoint and response sizes; making a buffer smaller without checking compatibility can produce intermittent failures rather than a reliable memory saving.
Re: ESP8266 HTTPS runs out of heap: how can TLS memory be reduced safely?
#4Keep server authentication and hostname validation intact. Certificate-based validation also needs an appropriate time source for validity checks. Reuse connections when supported, stream response processing and budget memory for the complete application instead of treating insecure mode as a solution to handshake failures.