Skip to content

[Bug]: HTTPS SSL_new_failed on ESP32 - both in 2.6.4 and 2.6.10 #6960

Description

@pleasantone

Category

WiFi, Hardware Compatibility

Hardware

T-Beam S3

Is this bug report about any UI component firmware like InkHUD or Meshtatic UI (MUI)?

  • Meshtastic UI aka MUI colorTFT
  • InkHUD ePaper
  • OLED slide UI on any display

Firmware Version

2.6.10

Description

Flash Lilygo T-Beam (ESP32) with either 2.6.4 or 2.6.10.
Include the embedded web ui.
Configure Lora region.
Configure the network.
Reboot
Never see the "setting up SSL keys message" appear after first reboot.

Attempt to go to https:// of unit.
Never connects.
Check console logs...

Does not appear on a T-Beam Supreme with 2.6.10 or a Station G2 with 2.6.10 which are both esp32s3, while the t-beam is an esp32 iirc.

[HTTPS:I] New connection. Socket FID=52
[HTTPS:E] SSL_new failed. Aborting handshake. FID=52
[HTTPS:I] Connection closed. Socket FID=52
[HTTPS:I] New connection. Socket FID=52
[HTTPS:E] SSL_new failed. Aborting handshake. FID=52
[HTTPS:I] Connection closed. Socket FID=52

Relevant log output

[HTTPS:I] New connection. Socket FID=52
[HTTPS:E] SSL_new failed. Aborting handshake. FID=52
[HTTPS:I] Connection closed. Socket FID=52
[HTTPS:I] New connection. Socket FID=52
[HTTPS:E] SSL_new failed. Aborting handshake. FID=52
[HTTPS:I] Connection closed. Socket FID=52

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions