Cannot call IFTTT maker webhooks from device - SSL error

#1

I have configured an IFTTT maker webhook, which when opened through browser works and I get a notification.

Howevery when I send it from the ESP8266 device:

HTTP.query({

            url: 'https://maker.ifttt.com/trigger/MY_TOPIC/with/key/MY_KEY',

            headers: { 'Content-Type': 'application/json'},

            success: function(){

                print('Notification sent successfully...');              

            },

            error: function(err){

                print('Notification not sent, error: ' + err);              

            },

    });

I keep getting a ssl error

[Jan 23 12:57:09.800] mongoose.c:4912         0x3fff72e4 ciphersuite: TLS-ECDHE-RSA-WITH-AES-128-GCM-SHA256
[Jan 23 12:57:10.466] E:M 516 (65 blocks)
[Jan 23 12:57:10.500] E:M 516 (65 blocks)
[Jan 23 12:57:10.518] E:M 524 (66 blocks)
[Jan 23 12:57:10.567] E:M 528 (67 blocks)
[Jan 23 12:57:10.650] E:M 516 (65 blocks)
[Jan 23 12:57:10.683] E:M 516 (65 blocks)
[Jan 23 12:57:10.717] E:M 524 (66 blocks)
[Jan 23 12:57:10.750] E:M 528 (67 blocks)
[Jan 23 12:57:10.834] E:M 516 (65 blocks)
[Jan 23 12:57:10.866] E:M 516 (65 blocks)
[Jan 23 12:57:10.884] mongoose.c:4912         0x3fff72e4 x509_verify_cert returned -9984
[Jan 23 12:57:10.884] mongoose.c:4912         0x3fff72e4   The certificate is not correctly signed by the trusted CA
[Jan 23 12:57:10.901]   The certificate is signed with an unacceptable hash.
[Jan 23 12:57:10.901] 
[Jan 23 12:57:10.901] mongoose.c:5088         0x3fff72e4 mbedTLS error: -0x2700
[Jan 23 12:57:10.983] Notification not sent, error:  
[Jan 23 12:57:11.001] mgos_mongoose.c:66      New heap free LWM: 264

I also checked the example here https://github.com/Tommystus/iftttMaker
I tried to add some ca certificates to ca.pem, but did not help.
Is my ca.pem incomplete or wrong ?

#2

You have some out of memory messages in the log

[Jan 23 12:57:10.466] E:M 516 (65 blocks)
[Jan 23 12:57:10.500] E:M 516 (65 blocks)
[Jan 23 12:57:10.518] E:M 524 (66 blocks)
[Jan 23 12:57:10.567] E:M 528 (67 blocks)
[Jan 23 12:57:10.650] E:M 516 (65 blocks)
[Jan 23 12:57:10.683] E:M 516 (65 blocks)
[Jan 23 12:57:10.717] E:M 524 (66 blocks)
[Jan 23 12:57:10.750] E:M 528 (67 blocks)
[Jan 23 12:57:10.834] E:M 516 (65 blocks)
[Jan 23 12:57:10.866] E:M 516 (65 blocks)

This issue might be related to that.

#3

Found a similar topic

So, there is no solution to the problem when making a SSL POST query in JS ?