-
Notifications
You must be signed in to change notification settings - Fork 13.3k
repeatable connection failure with AWS API #2845
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Have you tried the Try using just: I know that I never put the protocol prefix on hostnames ... just a thought? |
@Humancell - Good eye but that's not the issue. I added the prefix as one of my last attempts at getting it to work but I didn't strip it out before posting the example sketch. Thanks for catching this. I'll fix the sample sketch. |
For what it's worth, there was this commit in the axTLS repository which may be of interest: igrr/axtls-8266@b20140f |
@bantaj I was able to get a reliable connection to AWS API Gateway + Lambda using the wifi client. Seems to be issues with other versions of this ESP8266 Core for Arduino ... I was having problems with the git downloaded version. |
BearSSL is merged in #4273 , with alternate BearSSL::WiFi* classes. Although axtls-based classes are still available and even the default, they are planned for deprecation and then retirement, hence won't be fixed. Any issues with BearSSL-based classes should be reported in new issues. |
Hardware
Hardware: ESP-12
Core Version: 2.0.0
Description
I am getting repeatable connection failures when trying to make get or post requests to AWS API here: https://fptvt4j3ek.execute-api.us-west-2.amazonaws.com/Temp/mydemoresource
I am able to make similar get requests from other (non-AWS) servers that are also using TLS 1.2 according to their certificate details so it seems this may be an issue with the ESP8266 arduino core.
Settings in IDE
Module: Generic ESP8266 Module
Flash Size: 4MB/1MB
CPU Frequency: 80Mhz
Flash Mode: qio
Flash Frequency: 40Mhz
Upload Using: SERIAL
Sketch
Here's the serial output showing the connection failure:
The text was updated successfully, but these errors were encountered: