esp8266 / Arduino

ESP8266 core for Arduino
GNU Lesser General Public License v2.1
16.05k stars 13.33k forks source link

Can't connect to AWS IoT #5054

Closed torntrousers closed 6 years ago

torntrousers commented 6 years ago

Apologies if this is duplicate or a known issue but searching around I can't tell if it should work or not.

Basic Infos

Platform

Settings in IDE

Problem Description

Trying to connect to AWS IoT using MQTT with the sketch here: https://github.com/HarringayMakerSpace/awsiot/blob/master/Esp8266AWSIoTExample/Esp8266AWSIoTExample.ino

This used to work with the esp8266/arduino git code end of Dec 2017 but it doesn't now with the latest git code as of today.

With debug on this is the output:

SDK:2.2.1(cfd48f3)/Core:win-2.5.0-dev/lwIP:1.4.0rc2/BearSSL:6d1cefc

ESP8266 AWS IoT Example
Connecting to BTHub6-RX2Fscandone
scandone
state: 0 -> 2 (b0)
state: 2 -> 3 (0)
state: 3 -> 5 (10)
add 0
aid 8
cnt 

connected with BTHub6-RX2F, channel 6
dhcp client start...
ip:192.168.1.239,mask:255.255.255.0,gw:192.168.1.254
, WiFi connected, IP address: 192.168.1.239
=== CERTIFICATE ISSUED TO ===
Common Name (CN):       AWS IoT Certificate
Organization (O):       <Not Part Of Certificate>
Basic Constraints:      critical, CA:FALSE, pathlen:10000
Key Usage:          critical, Digital Signature
=== CERTIFICATE ISSUED BY ===
Common Name (CN):       <Not Part Of Certificate>
Organization (O):       <Not Part Of Certificate>
Organizational Unit (OU):   Amazon Web Services O=Amazon.com Inc. L=Seattle ST=Washington C=US
Not Before:         Thu Aug 16 13:53:28 2018
Not After:          Tue Nov 25 17:31:43 1913
RSA bitsize:            2048
Sig Type:           SHA256
PubSubClient connecting to: aebmz9k7b83pa.iot.us-east-1.amazonaws.com.State:    sending Client Hello (1)
State:  receiving Server Hello (2)
State:  receiving Certificate (11)
=== CERTIFICATE ISSUED TO ===
Common Name (CN):       *.iot.us-east-1.amazonaws.com
Organization (O):       Amazon.com, Inc.
Location (L):           Seattle
Country (C):            US
State (ST):         Washington
Basic Constraints:      CA:FALSE, pathlen:10000
Key Usage:          critical, Digital Signature, Key Encipherment
Subject Alt Name:       iot.us-east-1.amazonaws.com *.iot.us-east-1.amazonaws.com 
=== CERTIFICATE ISSUED BY ===
Common Name (CN):       Symantec Class 3 Secure Server CA - G4
Organization (O):       Symantec Corporation
Organizational Unit (OU):   Symantec Trust Network
Country (C):            US
Not Before:         Mon Nov 27 00:00:00 2017
Not After:          Wed Nov 28 23:59:59 2018
RSA bitsize:            2048
Sig Type:           SHA256
=== CERTIFICATE ISSUED TO ===
Common Name (CN):       Symantec Class 3 Secure Server CA - G4
Organization (O):       Symantec Corporation
Organizational Unit (OU):   Symantec Trust Network
Country (C):            US
Basic Constraints:      critical, CA:TRUE, pathlen:0
Key Usage:          critical, Key Cert Sign, CRL Sign
Subject Alt Name:       
=== CERTIFICATE ISSUED BY ===
Common Name (CN):       VeriSign Class 3 Public Primary Certification Authority - G5
Organization (O):       VeriSign, Inc.
Organizational Unit (OU):   VeriSign Trust Network
Country (C):            US
Not Before:         Thu Oct 31 00:00:00 2013
Not After:          Mon Oct 30 23:59:59 2023
RSA bitsize:            2048
Sig Type:           SHA256
State:  receiving Certificate Request (13)
State:  receiving Server Hello Done (14)
State:  sending Certificate (11)
State:  sending Client Key Exchange (16)
State:  sending Certificate Verify (15)
State:  sending Finished (16)
State:  receiving Finished (16)
Alert: close notify
torntrousers commented 6 years ago

Closing. I think this was due to a config issue at the AWS end.