-
Notifications
You must be signed in to change notification settings - Fork 13.3k
WiFiClientSecure client ipv4 always connect fail #4807
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
@earlephilhower could you please assess this? |
Unless @iamneo2416 can reproduce this on a public website, there's nothing to even test with. axTLS can connect to the majority of https websites, so there's something unique in his TLS server. My guess is this is the same problem as others where the server is sending multiple messages in a single fragment, which breaks axTLS but not (all?) other SSL implementations like the one used in full fat browsers/etc. |
Issue #3661 would be the original one. May be a 1-line patch to axtls suggested, but w/o a reproducible test case it's hard to say by inspection alone. |
@earlephilhower Does bearssl have this issue? |
@devyte BearSSL shouldn't have this issue, assuming it's a duplicate of #3661, as it is specific to the axtls lib parsing of TLS messages. I also just saw the text also shows a certificate with a silly "not after" date for the CA cert (> 2038, which axtls doesn't support so Hello 1982!) which is also an axtls specific thing. BearSSL should work for this. @iamneo2416 can try a CA that's valid only until 2037, which may make things work. Unless we get feedback from him about it after trying this, or if it still fails we'd still need a public website or this will not be reproducible. |
Maybe you can refer to #1460 . |
Closing due to lack of feedback from OP. |
Hardware:
Board: ESP8266 NodeMCU V2
Core Installation/update date: 2018/03/21
IDE name: Arduino IDE
Flash Frequency: 80Mhz
Upload Speed: 115200
Description:
All samples from internet use host name to do sample code. Today, I tried to use ipv4 to do sample code connection, but always get fail result without any luck. Here is my sample code. Please help. My server is located inside "intranet", not "internet".
I installed ubuntu 16.04 apache web server with self-signed certificate in LAN environment and use browser to access https://192.168.1.210/ web page always successfully.
I even use dos command line to telnet 192.168.1.210 443 to check port listening. It's working perfectly.
C:> telnet 192.168.1.210 443
But when I use WiFiClientSecure client.connect(ip, 443). It always get fail return. Is this a bug for ipv4 connect in connect() function ?
Here is the exact step I followed to build this virtual machine (192.168.1.210) w/self-signed certificate.
https://www.digitalocean.com/community/tutorials/how-to-create-a-self-signed-ssl-certificate-for-apache-in-ubuntu-16-04
Sketch:
The text was updated successfully, but these errors were encountered: