HTTPS / TLS STM - STM32H745-DISCO

[TalGadasiEnercon]

Hi, I'm using Mongoose Wizard with the STM32H745-DISCO board in CubeIDE (bare metal) to generate a web UI with HTTPS support. After generating the project, I enter the IP address I configured into the browser. HTTP (port 80) works fine, but when I try to access it via HTTPS on port 443, it doesn't work.

Besides setting the IP configuration so i wont use DHCP, is there anything else I need to change to enable HTTPS?( I am using the default cert and key.)

More details

1. I generate code via web
   

2. I change 3 lines of code (static IP instead of DHCP
Before
// #define MG_TCPIP_IP MG_IPV4(192, 168, 0, 10) // IP // #define MG_TCPIP_GW MG_IPV4(192, 168, 0, 1) // Gateway // #define MG_TCPIP_MASK MG_IPV4(255, 255, 255, 0) // Netmask

After
#define MG_TCPIP_IP MG_IPV4(169, 254, 0, 10) // IP #define MG_TCPIP_GW MG_IPV4(169, 254, 0, 1) // Gateway #define MG_TCPIP_MASK MG_IPV4(255, 255, 0, 0) // Netmask

I program the micro via STM32IDE

4. Mongoose server logs from UART
0 2 mongoose.c:21814:mg_phy_init PHY ID: 0x07 0xc111 (LAN87x) 6 2 mongoose.c:4151:mg_mgr_init Driver: stm32h, MAC: 02:42:c0:06:19:36 d 2 mongoose_impl.c:846:mongoose_i Starting HTTP listener 13 3 mongoose.c:4078:mg_listen 1 0 http://0.0.0.0:80 19 2 mongoose_impl.c:850:mongoose_i Starting HTTPS listener 1f 3 mongoose.c:4078:mg_listen 2 0 https://0.0.0.0:443 24 2 mongoose_impl.c:888:mongoose_i Mongoose init complete 2a 1 mongoose.c:5129:mg_tcpip_poll Network is down 3ee 1 mongoose.c:5129:mg_tcpip_poll Network is down 7d6 3 mongoose.c:23554:mg_tcpip_driv Link is 100M full-duplex 7dc 1 mongoose.c:4375:onstatechange Got IP bbe 2 mongoose.c:4371:onstatechange READY, IP: 169.254.0.10 bc3 2 mongoose.c:4372:onstatechange GW: 169.254.0.1 bc9 2 mongoose.c:4373:onstatechange MAC: 02:42:c0:06:19:36

5.HTTP (port 80) is working

6. HTTPS cant connect
   

7. Wireshark and bash logs while try https
   wireshark https.txt

`
H:>curl -vk https://169.254.0.10

• Trying 169.254.0.10:443...
• schannel: disabled automatic use of client certificate
• schannel: using IP address, SNI is not supported by OS.
• ALPN: curl offers http/1.1
• schannel: next InitializeSecurityContext failed: SEC_E_ALGORITHM_MISMATCH (0x80090331) - The client and server cannot communicate, because they do not possess a common algorithm.
• closing connection #0
  curl: (35) schannel: next InitializeSecurityContext failed: SEC_E_ALGORITHM_MISMATCH (0x80090331) - The client and server cannot communicate, because they do not possess a common algorithm.`

[scaprile]

Please contact Support

[TalGadasiEnercon]

Apologies for the lack of details earlier. I've added much more information now and hope you can help me.

[scaprile]

Please contact Support

I've been informed you are a prospect, please contact Support. I've already pushed 8061a41 to this repo yesterday, that will propagate to the Wizard in due time.

[TalGadasiEnercon]

Ok tank you, I will contact Support. By the way i did change manually dmss to 1460 and it is works. I get the warring because lack of CA as excepted.