Help with HTTPS #784

torntrousers · 2015-09-14T20:08:12Z

I'm trying to use the new https support but can't get it to work so wonder if someone could see what the problem is (sorry if this is leaping ahead, i know the https code hasn't been released yet). I've built the latest git code from today (1f8c14d) and started with the HTTPSRequest sample. That works ok (though does always seem to get a wdt reset after closing the connection), so i then changed it to do a GET to https://www.btopenzone.com:8443, and that worked ok too, so then updated it to try to do a POST to http://www.btopenzone.com:8443/tbbLogon but that doesn't work and all i get back is a stream of ÿ characters.

This is the code i have, can anyone see a problem?

/*
 *  HTTP over TLS (HTTPS) example sketch
 *
 *  This example demonstrates how to use
 *  WiFiClientSecure class to access HTTPS API.
 *  We fetch and display the status of
 *  esp8266/Arduino project continous integration
 *  build.
 *
 *  Created by Ivan Grokhotkov, 2015.
 *  This example is in public domain.
 */

#include <ESP8266WiFi.h>
#include <WiFiClientSecure.h>

const char* ssid = "BTHub5-72W5";
const char* password = "xxxxxxxxxxx";

//const char* host = "api.github.com";
//const int httpsPort = 443;
const char* host = "www.btopenzone.com";
const int httpsPort = 8443;

// Use web browser to view and copy
// SHA1 fingerprint of the certificate
const char* fingerprint = "CF 05 98 89 CA FF 8E D8 5E 5C E0 C2 E4 F7 E6 C3 C7 50 DD 5C";

void setup() {
  Serial.begin(115200);
  Serial.println();
  Serial.print("connecting to ");
  Serial.println(ssid);
  WiFi.begin(ssid, password);
  while (WiFi.status() != WL_CONNECTED) {
    delay(500);
    Serial.print(".");
  }
  Serial.println("");
  Serial.println("WiFi connected");
  Serial.println("IP address: ");
  Serial.println(WiFi.localIP());

  // Use WiFiClientSecure class to create TLS connection
  WiFiClientSecure client;
  Serial.print("connecting to ");
  Serial.println(host);
  while (!client.connect(host, httpsPort)) {
    Serial.println("connection failed");
//    return;
  }

  if (client.verify(fingerprint, host)) {
    Serial.println("certificate matches");
  } else {
    Serial.println("certificate doesn't match");
  }

//  String url = "/repos/esp8266/Arduino/commits/esp8266/status";
  String url = "/tbbLogon";
  String postData = "username=qaz123@btinternet.com&password=abc123&xhtmlLogon=https://www.btopenzone.com:8443/tbbLogon";
  Serial.print("requesting URL: ");
  Serial.println(url);
/*
  client.print(String("POST ") + url + " HTTP/1.1\r\n" +
               "Host: " + host + "\r\n" +
               "User-Agent: BuildFailureDetectorESP8266\r\n" +
               "Connection: close\r\n\r\n");
*/
  client.print("POST /tbbLogon HTTP/1.1\n");
  client.print("Host: www.btopenzone.com:8443\n");
  client.print("Connection: close\n");
//  client.print("Connection: keep-alive\n");
//  client.print("User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Firefox/38.0\n");
  client.print("Content-Type: application/x-www-form-urlencoded\n");
  client.print("Content-Length: ");
  client.print(postData.length()+2);
  client.print("\n\n");
  client.print(postData);

  Serial.println("request sent");

  Serial.println("Receiving response");

  while (client.connected()) {
    /*
    String line = client.readStringUntil('\n');
    Serial.println(line);
    if (line == "\r") {
      Serial.println("headers received");
      break;
    }
    */
    Serial.write(client.read());
    delay(10);
  }
  Serial.println("2");
  String line = client.readStringUntil('\n');
  Serial.println(line);
  Serial.println("closing connection");
}

void loop() {
    delay(1000);
    Serial.println("done");
}

As an alternative test this does work and returns an html page:

curl --data "username=qaz123%40btinternet.com&password=abc123&xhtmlLogon=https://www.btopenzone.com:8443/tbbLogon" https://www.btopenzone.com:8443/tbbLogon

The text was updated successfully, but these errors were encountered:

igrr · 2015-09-14T20:16:12Z

Serial.write(client.read());

When there is no character to be read, client.read() returns -1, which is then converted to a character by Serial.write. This results in a character with ASCII code of 255, which may look like ÿ depending on the terminal. You might want to check if client.available() > 0 before calling read.

There may be other issues, but this one is the most obvious.

Edit: perhaps you are not getting the reply because the server is expecting two more characters?

 client.print(postData.length()+2);

And then you send just postData.length() characters after the headers.

torntrousers · 2015-09-14T20:30:17Z

Ah ok, i should have known that. But i did have the client.available() check before and then it just hangs never getting back a response. Trying again now adding this code after the Serial.println("Receiving response") then it just sits forever printing out dots:

  while (client.available() < 1) {
    Serial.print(".");
    delay(100);
  }

igrr · 2015-09-14T20:32:17Z

What happens if you change Content-Length header to match the real size of content?

Links2004 · 2015-09-14T20:33:28Z

your header lineending need to be \r\n look in the http RFC for more info

torntrousers · 2015-09-14T20:46:22Z

Something like this?

  client.print("POST /tbbLogon HTTP/1.1\r\n");
  client.print("Host: www.btopenzone.com:8443\r\n");
  client.print("Connection: close\r\n");
  client.print("Content-Type: application/x-www-form-urlencoded\r\n");
  client.print("Content-Length: ");
  client.print(postData.length());
  client.print("\r\n");
  client.print(postData);
  Serial.println("request sent");
  Serial.println("Receiving response");

  while (client.available() < 1) {
    Serial.print(".");
    delay(100);
  }

Still just dots and no response comes back.

igrr · 2015-09-14T20:52:06Z

You still seem to be missing an empty line after the headers (see the \r\n\r\n sequence in the original example).

torntrousers · 2015-09-14T21:10:41Z

Ok, rearranging to be more closely like the original example:

  client.print(String("POST ") + url + " HTTP/1.1\r\n" +
               "Host: " + host + "\r\n" +
               "User-Agent: BuildFailureDetectorESP8266\r\n" +
               "Content-Type: application/x-www-form-urlencoded\r\n" +
               "Content-Length: " + postData.length() + "\r\n" +
               "Connection: close\r\n\r\n");

  client.print(postData);

  Serial.println("request sent");
  Serial.println("Receiving response");

  while (client.available() < 1) {
    Serial.print(".");
    delay(100);
  }

but still just dots and no response.

torntrousers · 2015-09-15T08:35:37Z

Now i've tried running tcpmon on a local computer with a local non-ssl http port being forwarded to www.btopenzone.com port 8443 as SSL, and then changing the esp sketch to use WiFiClient instead of WiFiClientSecure and to use the tcpmon host address, but the rest of the sketch unchanged.
That works, tcpmon forwards the post request to btopenzone as ssl which returns an html response which the esp sketch receives and prints out. So the esp sketch must be formating the POST request and headers ok.
What else could the problem be, some bug with WiFiClientSecure?

igrr · 2015-09-15T08:47:20Z

Correct, if the same POST request works with WiFiClient then it's likely a bug in WiFiClientSecure.

Links2004 · 2015-09-15T14:49:47Z

at every print you send a tcp package some servers dont like this.
you can try it like this:
#773 (comment)

you also shut have "\r\n\r\n" before postData or the server will interpreter it as invalidate request.

torntrousers · 2015-09-15T17:57:41Z

Getting a bit further...i think there might be a bug in WifiClientSecure - it looks like after sending the request client.available() is always returning 0 even when a response has come back, but doing client.readStringUntil('\n') does return the first line, and then client.available() starts working properly. You can see this by modifying the HTTPSRequest sample to have a while loop printing client.available() before and after the client.readStringUntil call.

So accounting for that i can get the https POST to work ok, yipee!

Unfortunately it still doesn't work for what i want, which is trying to have the ESP logon to a FON Wifi network. Not really for this git issue but i wonder if it needs to have two connections, one for the https connection which is kept open and another to do the other http requests on - can the esp do multiple client connections?

Links2004 · 2015-09-15T19:02:21Z

yes up to 5 TCP and 4 UDP connections at one time.

Arduino/hardware/esp8266com/esp8266/libraries/ESP8266WiFi/src/lwip/opt.h

Line 243 in ea302aa

#define MEMP_NUM_UDP_PCB 4

torntrousers · 2015-09-15T20:01:12Z

Ok thanks for confirming that. Doing some debugging with netstat on a pc i don't think it uses multiple connections anyway. Not sure how it works, in case anyone has any suggestions here's what happens:

There are lots of FON access points named (in the UK) BTWifi-with-FON that are open with no security. So you connect to them and then if you try to use a browser then you can't connect to anything until you go to a FON web page with a form where you have to logon with a userid password, and then after that you're connected and all internet access works normally (for a short while after which you need to reenter the userid/password again).

I traced the web page form and it just does a POST with the userid/password so now i can replicate the logon with a curl command instead of using the web page form: curl --data "username=qaz123%40btinternet.com&password=abc123&xhtmlLogon=https://www.btopenzone.com:8443/tbbLogon" https://www.btopenzone.com:8443/tbbLogon

So i was hoping to replicate that on an ESP and do the https post and then be able to make other http connections to publish data. The https post seems to work fine and the headers and response the esp gets back look the same as what the curl command gets, but then further WifiClient requests on the ESP don't work and just fail to connect.

I thought it might just be using the mac address against the userid/password or somehting like that but i guess there must be more to it.

Any ideas?

Links2004 · 2015-09-15T20:14:22Z

for me this looks like the FON access points runs a transparent proxy.
so the allow your ip or mac for some time to use the proxy.
where do you try to connect to? may they only allow some ports / protocols.

torntrousers · 2015-09-15T20:43:24Z

It started working! Don't know what i did, just tidied the code up a bit i thought, but now it works ok. Very pleased. Thanks for all the help.

Would be good to get the WifiClientSecure.available bug fixed though so i'll leave this open for that.

torntrousers · 2015-09-18T08:30:20Z

Thanks for the fix, i can confirm it does fix it for me.

Attempt to read data from SSL engine inside WiFiClientSecure::available() if RX buffer is empty. Fix #784.

YONG81K · 2015-11-14T10:43:22Z

Torntrousers, I would love to try out HTTPS request from ESP, could you tell me where can I download the WiFiClientSecure lib please? Thank you.

gicho · 2015-11-14T12:59:35Z

You should install the staging version of the ESP8266-Arduino libraries using this URL for board manager in preferences:
http://arduino.esp8266.com/staging/package_esp8266com_index.json

YONG81K · 2015-11-14T17:46:00Z

Thanks gicho, actually I already have HTTP working with ESP-12E board using this URL for board manager in preferences: http://arduino.esp8266.com/versions/1.6.5-1160-gef26c5f/package_esp8266com_index.json. Updated the ESP8266WIFI lib and the compiler is recognizing the WiFiClientSecure.h now. I ran the example above, it connected, certificate matches but the return file config.htm has 0 Bytes (File /config.htm 0 Bytes). Web Browser (https://raw.githubusercontent.com/sticilface/ESPmanager/Strings/examples/Settingsmanager-example/data/config.htm) return differently. Any idea? Thank you in advance.

Links2004 · 2015-11-14T18:09:09Z

may its the same problem then here:
#43 (comment)

its most likely the TLS fragment size that is to big.
the ESP can only handle SSL / TLS fragment size of 4K.

electronicsguy · 2016-03-29T02:28:00Z

@Links2004 @gicho @torntrousers Can someone tell me if I can make HTTPS GET requests using ESP-01? Or is it only possible on the models with more memory?

Links2004 · 2016-03-29T05:12:29Z

You can all esp8266 has the same ram size, only the flash is different.
Am 29.03.2016 4:28 vorm. schrieb "Sujay Phadke" notifications@github.com:

@Links2004 https://github.com/Links2004 @gicho
https://github.com/gicho @torntrousers https://github.com/torntrousers
Can someone tell me if I can make HTTPS GET requests using ESP-01? Or is it
only possible on the models with more memory?

—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#784 (comment)

sreeramtkd · 2017-02-12T17:15:55Z

Is there a fix for this ? I'm trying to connect to the below URL and getting the -1 as output or at times an empty string is passed to serial output.

https://api.apifier.com/v1/execs/APIKEY/results

electronicsguy · 2017-02-12T17:26:58Z

@sreeramtkd Yes ESP-01 works with SSL over http. Use the WifiClientSecure library here: WiFiClientSecure

sreeramtkd · 2017-02-12T17:36:27Z

@electronicsguy I'm using the latest library but unfortunately I can't get esp8266 to pull https data

connecting to Sree
..............
WiFi connected
IP address:
192.168.1.4
connecting to api.apifier.com
Certificate matches
requesting URL: /v1/execs/To5wxSEcGZGYzLurA/results
request sent
reply was:

String is
ÿ

closing connection

electronicsguy · 2017-02-12T17:38:52Z

@sreeramtkd Well the library does have some restrictions as @igrr has mentioned in the documentation for it. (like encryption type, max. certificate size, etc). But you need to post your code with a minimal example for others to check.

sreeramtkd · 2017-02-12T17:41:12Z

Here is the code from library

#include <ESP8266WiFi.h>
#include <WiFiClientSecure.h>

const char* ssid = "";
const char* password = "";

const char* host = "api.apifier.com";
const int httpsPort = 443;

// Use web browser to view and copy
// SHA1 fingerprint of the certificate
const char* fingerprint = "17 67 4C 08 F1 22 7B B4 1C 6F 5B 01 22 AB 00 06 24 8E D8 6B";

void setup() {
Serial.begin(115200);
Serial.println();
Serial.print("connecting to ");
Serial.println(ssid);
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED) {
delay(500);
Serial.print(".");
}
Serial.println("");
Serial.println("WiFi connected");
Serial.println("IP address: ");
Serial.println(WiFi.localIP());
// Use WiFiClientSecure class to create TLS connection
WiFiClientSecure client;
Serial.print("connecting to ");
Serial.println(host);
if (!client.connect(host, httpsPort)) {
Serial.println("connection failed");
return;
}

if (client.verify(fingerprint, host)) {
Serial.println("Certificate matches");
} else {
Serial.println("Certificate doesn't match");
}
String url = "/v1/execs/To5wxSEcGZGYzLurA/results";
Serial.print("requesting URL: ");
Serial.println(url);
client.print(String("GET ") + url + " HTTP/1.1\r\n" +
"Host: " + host + "\r\n" +
"Connection: close\r\n\r\n");
Serial.println("request sent");
int repeatCounter = 10;
while (!client.available() && repeatCounter--) {
delay(500);
}
String line;
line = client.readStringUntil('\n');
Serial.println("reply was:");
Serial.println("==========");
Serial.println(line);
Serial.println("==========");
Serial.println("closing connection");
}
void loop() {
}

sreeramtkd · 2017-02-12T17:42:58Z

also FYI i'm using an ESP8266 12-F module

electronicsguy · 2017-03-30T22:17:39Z

@sreeramtkd apifier works for me using HTTPSRedirect. Please check it out:

This is what I get as the expected output:
"_id": "<id removed>", "actId": "CwNxxSNdBYw7NWLjb", "startedAt": "2017-02-13T14:54:44.162Z", "finishedAt": "2017-02-13T14:54:56.197Z", "status": "SUCCEEDED", "statusMessage": "Crawled 5 pages, limit is 5 pages", "tag": null, "stats": { "downloadedBytes": 153322, "pagesInQueue": 0, "pagesCrawled": 5, "pagesOutputted": 5, "pagesFailed": 0, "pagesCrashed": 0, "pagesRetried": 0, "totalPageRetries": 0, "storageBytes": 17992 }, "meta": { "source": "API", "method": "POST", "clientIp": "redacted", "userAgent": "redacted" }, "detailsUrl": "https://api.apifier.com/v1/execs/<id redacted>", "resultsUrl": "https://api.apifier.com/v1/execs/<id redacted>/results" }

evbelda · 2017-04-17T10:06:19Z

Hi,

I'm trying to use the ESP-01 module+Mega conect to TX/RX 18 and 19 Pin but it doesn't work with ESP8266Wifi library.
How do you configure the board to accept a Mega (only accept ESP8266 boards) with an ESP module?
How do you connect the ESP-01 module pins to work?

sherikapotein · 2017-06-04T04:40:34Z

Hi,

Going through various related posts I could get my Wemos to send and accept https requests. Chhers to the community for that !! :). I'd used the similar code as shared by @sreeramtkd above.

For purpose of testing I'd used a free webhost(Heliohost) and used a LetsEncrypt SSL certificate and it worked smoothly.

My end goal was to implement the same functionality on my local network where my Wemos/ESPs would communicate with a server running Nginx and communicate over https. I could setup the Nginx with a self signed certificate as instructed here.

I did not wish to have any sorts of Internet connectivity from my local network, because of which I could not use the same LetsEncrypt certificate again.

After setting up the Nginx, the Wemos is unable to connect to the server on port 443 using Https but can communicate with it over port 80. It gives a plain "connection failed". I could have moved ahead had the error been related to certifate, wrong fingerprint or something which happens after connection is established. But a refusal to connect keeps me hanging. Tried to skim through the source code but its probably over my limited knowledge.

I have verified port 443 (for Https) to be open and accessible by browser clients on the network.

Some inputs on troubleshooting please.
EDIT: Upon further investigation I stumbled across this post. Placing the output of sslscan:

Testing SSL server localhost on port 443

  Supported Server Cipher(s):
    Failed    TLSv1  256 bits  ECDHE-RSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  ECDHE-ECDSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  ECDHE-RSA-AES256-SHA384
    Failed    TLSv1  256 bits  ECDHE-ECDSA-AES256-SHA384
    Accepted  TLSv1  256 bits  ECDHE-RSA-AES256-SHA
    Rejected  TLSv1  256 bits  ECDHE-ECDSA-AES256-SHA
    Failed    TLSv1  256 bits  SRP-DSS-AES-256-CBC-SHA
    Failed    TLSv1  256 bits  SRP-RSA-AES-256-CBC-SHA
    Failed    TLSv1  256 bits  SRP-AES-256-CBC-SHA
    Failed    TLSv1  256 bits  DH-DSS-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  DHE-DSS-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  DH-RSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  DHE-RSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  DHE-RSA-AES256-SHA256
    Failed    TLSv1  256 bits  DHE-DSS-AES256-SHA256
    Failed    TLSv1  256 bits  DH-RSA-AES256-SHA256
    Failed    TLSv1  256 bits  DH-DSS-AES256-SHA256
    Accepted  TLSv1  256 bits  DHE-RSA-AES256-SHA
    Rejected  TLSv1  256 bits  DHE-DSS-AES256-SHA
    Rejected  TLSv1  256 bits  DH-RSA-AES256-SHA
    Rejected  TLSv1  256 bits  DH-DSS-AES256-SHA
    Rejected  TLSv1  256 bits  DHE-RSA-CAMELLIA256-SHA
    Rejected  TLSv1  256 bits  DHE-DSS-CAMELLIA256-SHA
    Rejected  TLSv1  256 bits  DH-RSA-CAMELLIA256-SHA
    Rejected  TLSv1  256 bits  DH-DSS-CAMELLIA256-SHA
    Rejected  TLSv1  256 bits  AECDH-AES256-SHA
    Failed    TLSv1  256 bits  ADH-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  ADH-AES256-SHA256
    Rejected  TLSv1  256 bits  ADH-AES256-SHA
    Rejected  TLSv1  256 bits  ADH-CAMELLIA256-SHA
    Failed    TLSv1  256 bits  ECDH-RSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  ECDH-ECDSA-AES256-GCM-SHA384
    Failed    TLSv1  256 bits  ECDH-RSA-AES256-SHA384
    Failed    TLSv1  256 bits  ECDH-ECDSA-AES256-SHA384
    Rejected  TLSv1  256 bits  ECDH-RSA-AES256-SHA
    Rejected  TLSv1  256 bits  ECDH-ECDSA-AES256-SHA
    Failed    TLSv1  256 bits  AES256-GCM-SHA384
    Failed    TLSv1  256 bits  AES256-SHA256
    Rejected  TLSv1  256 bits  AES256-SHA
    Rejected  TLSv1  256 bits  CAMELLIA256-SHA
    Failed    TLSv1  256 bits  PSK-AES256-CBC-SHA
    Failed    TLSv1  128 bits  ECDHE-RSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  ECDHE-ECDSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  ECDHE-RSA-AES128-SHA256
    Failed    TLSv1  128 bits  ECDHE-ECDSA-AES128-SHA256
    Rejected  TLSv1  128 bits  ECDHE-RSA-AES128-SHA
    Rejected  TLSv1  128 bits  ECDHE-ECDSA-AES128-SHA
    Failed    TLSv1  128 bits  SRP-DSS-AES-128-CBC-SHA
    Failed    TLSv1  128 bits  SRP-RSA-AES-128-CBC-SHA
    Failed    TLSv1  128 bits  SRP-AES-128-CBC-SHA
    Failed    TLSv1  128 bits  DH-DSS-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  DHE-DSS-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  DH-RSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  DHE-RSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  DHE-RSA-AES128-SHA256
    Failed    TLSv1  128 bits  DHE-DSS-AES128-SHA256
    Failed    TLSv1  128 bits  DH-RSA-AES128-SHA256
    Failed    TLSv1  128 bits  DH-DSS-AES128-SHA256
    Rejected  TLSv1  128 bits  DHE-RSA-AES128-SHA
    Rejected  TLSv1  128 bits  DHE-DSS-AES128-SHA
    Rejected  TLSv1  128 bits  DH-RSA-AES128-SHA
    Rejected  TLSv1  128 bits  DH-DSS-AES128-SHA
    Rejected  TLSv1  128 bits  DHE-RSA-SEED-SHA
    Rejected  TLSv1  128 bits  DHE-DSS-SEED-SHA
    Rejected  TLSv1  128 bits  DH-RSA-SEED-SHA
    Rejected  TLSv1  128 bits  DH-DSS-SEED-SHA
    Rejected  TLSv1  128 bits  DHE-RSA-CAMELLIA128-SHA
    Rejected  TLSv1  128 bits  DHE-DSS-CAMELLIA128-SHA
    Rejected  TLSv1  128 bits  DH-RSA-CAMELLIA128-SHA
    Rejected  TLSv1  128 bits  DH-DSS-CAMELLIA128-SHA
    Rejected  TLSv1  128 bits  AECDH-AES128-SHA
    Failed    TLSv1  128 bits  ADH-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  ADH-AES128-SHA256
    Rejected  TLSv1  128 bits  ADH-AES128-SHA
    Rejected  TLSv1  128 bits  ADH-SEED-SHA
    Rejected  TLSv1  128 bits  ADH-CAMELLIA128-SHA
    Failed    TLSv1  128 bits  ECDH-RSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  ECDH-ECDSA-AES128-GCM-SHA256
    Failed    TLSv1  128 bits  ECDH-RSA-AES128-SHA256
    Failed    TLSv1  128 bits  ECDH-ECDSA-AES128-SHA256
    Rejected  TLSv1  128 bits  ECDH-RSA-AES128-SHA
    Rejected  TLSv1  128 bits  ECDH-ECDSA-AES128-SHA
    Failed    TLSv1  128 bits  AES128-GCM-SHA256
    Failed    TLSv1  128 bits  AES128-SHA256
    Rejected  TLSv1  128 bits  AES128-SHA
    Rejected  TLSv1  128 bits  SEED-SHA
    Rejected  TLSv1  128 bits  CAMELLIA128-SHA
    Failed    TLSv1  128 bits  PSK-AES128-CBC-SHA
    Rejected  TLSv1  128 bits  ECDHE-RSA-RC4-SHA
    Rejected  TLSv1  128 bits  ECDHE-ECDSA-RC4-SHA
    Rejected  TLSv1  128 bits  AECDH-RC4-SHA
    Rejected  TLSv1  128 bits  ADH-RC4-MD5
    Rejected  TLSv1  128 bits  ECDH-RSA-RC4-SHA
    Rejected  TLSv1  128 bits  ECDH-ECDSA-RC4-SHA
    Rejected  TLSv1  128 bits  RC4-SHA
    Rejected  TLSv1  128 bits  RC4-MD5
    Failed    TLSv1  128 bits  PSK-RC4-SHA
    Rejected  TLSv1  112 bits  ECDHE-RSA-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  ECDHE-ECDSA-DES-CBC3-SHA
    Failed    TLSv1  112 bits  SRP-DSS-3DES-EDE-CBC-SHA
    Failed    TLSv1  112 bits  SRP-RSA-3DES-EDE-CBC-SHA
    Failed    TLSv1  112 bits  SRP-3DES-EDE-CBC-SHA
    Rejected  TLSv1  112 bits  EDH-RSA-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  EDH-DSS-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  DH-RSA-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  DH-DSS-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  AECDH-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  ADH-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  ECDH-RSA-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  ECDH-ECDSA-DES-CBC3-SHA
    Rejected  TLSv1  112 bits  DES-CBC3-SHA
    Failed    TLSv1  112 bits  PSK-3DES-EDE-CBC-SHA
    Rejected  TLSv1  0 bits    ECDHE-RSA-NULL-SHA
    Rejected  TLSv1  0 bits    ECDHE-ECDSA-NULL-SHA
    Rejected  TLSv1  0 bits    AECDH-NULL-SHA
    Rejected  TLSv1  0 bits    ECDH-RSA-NULL-SHA
    Rejected  TLSv1  0 bits    ECDH-ECDSA-NULL-SHA
    Failed    TLSv1  0 bits    NULL-SHA256
    Rejected  TLSv1  0 bits    NULL-SHA
    Rejected  TLSv1  0 bits    NULL-MD5

  Prefered Server Cipher(s):
    TLSv1  256 bits  ECDHE-RSA-AES256-SHA

  SSL Certificate:
    Version: 2
    Serial Number: -10219921245213661837
    Signature Algorithm: sha256WithRSAEncryption
    Issuer: /C=###/ST=####/L=#####/O=####/OU=####/CN=192.168.1.105/emailAddress=######@#####.com
    Not valid before: May 27 11:53:32 2017 GMT
    Not valid after: May 27 11:53:32 2018 GMT
    Subject: /C=IN/ST=##/L=##/O=##/OU=Aut division/CN=192.168.1.105/emailAddress=########
    Public Key Algorithm: rsaEncryption
    RSA Public Key: (2048 bit)
      Public-Key: (2048 bit)
      Modulus:
          00:e1:42:e0:85:cb:8c:38:d3:63:bb:dd:50:a9:04:
          d6:75:6b:c2:42:e9:cf:08:ab:2c:f0:6f:12:48:a6:
          34:94:39:32:12:5c:87:5b:84:8e:ba:33:f7:69:7e:
          82:92:b9:1a:4e:69:27:20:05:db:48:d7:38:af:50:
          9b:f3:a1:f4:4b:cc:f4:63:f4:b8:73:11:fe:d3:cf:
          e9:2f:3e:c0:49:a3:b0:aa:e7:80:95:b1:ad:25:2a:
          a5:ff:7c:16:97:96:8c:89:5b:66:ae:b6:99:a7:4b:
          fd:97:46:d9:65:0e:a4:4f:89:e7:e9:0a:4e:76:0f:
          18:51:30:9b:5b:f8:5d:5f:0d:5f:2b:68:9c:ef:46:
          66:8e:0d:8d:58:73:91:37:87:e5:90:04:a3:52:4f:
          f4:1d:be:9d:05:e5:af:07:9d:b9:82:a3:24:22:4b:
          de:2d:1c:25:66:e4:fc:44:1c:c8:2b:44:3f:72:8d:
          2d:60:4b:49:f6:de:99:4f:b4:95:8d:49:d2:8d:0e:
          40:01:b2:4d:c4:6b:a6:4c:5b:89:47:5a:ca:7a:4b:
          d1:4c:72:54:d6:b3:07:0a:ad:67:f8:24:e1:00:4e:
          fd:4b:54:00:a8:ae:f4:6e:2e:af:1e:1f:61:a8:cc:
          65:a2:4a:22:b3:af:db:6f:6f:58:ec:c8:1a:fc:37:
          09:a7
      Exponent: 65537 (0x10001)
    X509v3 Extensions:
      X509v3 Subject Key Identifier: 
        5D:77:6E:F8:BD:C4:8C:16:FE:B3:F3:6F:97:77:66:5C:4D:80:DE:15
      X509v3 Authority Key Identifier: 
        keyid:5D:77:6E:F8:BD:C4:8C:16:FE:B3:F3:6F:97:77:66:5C:4D:80:DE:15

      X509v3 Basic Constraints: 
        CA:TRUE
  Verify Certificate:
    self signed certificate

AbdelsalamHaa · 2018-01-27T11:50:17Z

Hi
i'm trying to connect my esp8266 to my http server , i have read so many code and try to understand , a could understand few but im still not very clear how to do it . i think my problem is in the request message i really really hope someone can help me fixing it my code is here thanks in advance

#include <ESP8266WiFi.h>

const char* ssid = "-----------";
const char* password = "-------------";

const char* host = "35.187.233.153";

void setup()
{
Serial.begin(115200);
Serial.println();

Serial.printf("Connecting to %s ", ssid);
WiFi.begin(ssid, password);
while (WiFi.status() != WL_CONNECTED)
{
delay(500);
Serial.print(".");
}
Serial.println(" connected");
}

void loop()
{
WiFiClient client;

Serial.printf("\n[Connecting to %s ... ", host);
if (client.connect(host, 80))
{
Serial.println("connected]");

Serial.println("[Sending a request]");

client.print("POST ");
client.print("/api/trash/update?id=1&level=99&battL=9999");// here are the data i wanna transimte they are supposed to part of the url .
client.print(" HTTP/1.1\r\n");
client.print("Host:35.187.233.153\r\n");
client.print("Content-Type: application/x-www-form-urlencoded\n");

client.print("Connection: close\r\n");

Serial.println("[Response:]");
while (client.connected())
{
  if (client.available())
  {
  
    String line = client.readStringUntil('\n');
    Serial.println(line); 
  }
}
client.stop();
Serial.println("\n[Disconnected]");

}
else
{
Serial.println("connection failed!]");
client.stop();
}
delay(5000);
}

sreeramtkd · 2018-02-13T14:13:15Z

@AbdelsalamHaa - Would be nice to see the error / issue in specific, Use any of the available online client testing services to see if you are getting proper response from the server mentioned in code. https://www.hurl.it/ Or Postman Echo. This should allow you to debug issues.

AbdelsalamHaa · 2018-02-24T13:50:08Z

@sreeramtkd thanks for ur responds , I have actually found the problem which was in my request message format .

Craig1516 · 2018-03-07T17:20:12Z

AbdelsalamHaa, would you mind sharing your final code? Or does your Jan 27 post include final?

Thanks,
Craig

edugargon · 2019-02-05T23:19:49Z

Hi,

I'm trying to use the ESP-01 module+Mega conect to TX/RX 18 and 19 Pin but it doesn't work with ESP8266Wifi library.
How do you configure the board to accept a Mega (only accept ESP8266 boards) with an ESP module?
How do you connect the ESP-01 module pins to work?

I'm in the same situation but with an Arduino UNO and ESP-01 with SoftwareSerial.
I can not find a way to add a WiFiClientSecure instance to use as a gateway to UniversalTelegramBot, since the ESP8266WiFi.h library is not compatible with Arduino boards.
Has anyone been able to do it? Thank you very much.
Regards.

electronicsguy · 2019-02-08T02:58:50Z

@edugargon If you have a esp8266, what are you using Arduino for? Unless you need analog inputs, the arduino is unnecessary.

edugargon · 2019-02-09T00:01:04Z

@edugargon If you have a esp8266, what are you using Arduino for? Unless you need analog inputs, the arduino is unnecessary.

You said, if I'm using Arduino, it's because I need analog inputs.

klslowik · 2020-05-12T07:22:41Z

Hi,
I'm trying to use the ESP-01 module+Mega conect to TX/RX 18 and 19 Pin but it doesn't work with ESP8266Wifi library.
How do you configure the board to accept a Mega (only accept ESP8266 boards) with an ESP module?
How do you connect the ESP-01 module pins to work?

I'm in the same situation but with an Arduino UNO and ESP-01 with SoftwareSerial.
I can not find a way to add a WiFiClientSecure instance to use as a gateway to UniversalTelegramBot, since the ESP8266WiFi.h library is not compatible with Arduino boards.
Has anyone been able to do it? Thank you very much.
Regards.

I have the same problem right now.
Were you able to solve it?

JiriBilek · 2020-05-12T07:46:37Z

AFAIK this problem is not related to this repository. You can sort it out by flashing an AT firmware (from Espressif repository) to your ESP8266 board and use an Arduino library to communicate over serial (e.g. WifiEsp library).
But the communication via serial is far from perfect.

igrr closed this as completed in 89df285 Sep 16, 2015

igrr added a commit that referenced this issue Oct 29, 2015

WiFiClientSecure::available fix

5387b22

Attempt to read data from SSL engine inside WiFiClientSecure::available() if RX buffer is empty. Fix #784.

Help with HTTPS #784

Help with HTTPS #784

Comments

torntrousers commented Sep 14, 2015

igrr commented Sep 14, 2015

torntrousers commented Sep 14, 2015

igrr commented Sep 14, 2015

Links2004 commented Sep 14, 2015

torntrousers commented Sep 14, 2015

igrr commented Sep 14, 2015

torntrousers commented Sep 14, 2015

torntrousers commented Sep 15, 2015

igrr commented Sep 15, 2015

Links2004 commented Sep 15, 2015

torntrousers commented Sep 15, 2015

Links2004 commented Sep 15, 2015

torntrousers commented Sep 15, 2015

Links2004 commented Sep 15, 2015

torntrousers commented Sep 15, 2015

torntrousers commented Sep 18, 2015

YONG81K commented Nov 14, 2015

gicho commented Nov 14, 2015

YONG81K commented Nov 14, 2015

Links2004 commented Nov 14, 2015

electronicsguy commented Mar 29, 2016

Links2004 commented Mar 29, 2016

sreeramtkd commented Feb 12, 2017

electronicsguy commented Feb 12, 2017

sreeramtkd commented Feb 12, 2017 • edited Loading

@electronicsguy I'm using the latest library but unfortunately I can't get esp8266 to pull https data

connecting to Sree .............. WiFi connected IP address: 192.168.1.4 connecting to api.apifier.com Certificate matches requesting URL: /v1/execs/To5wxSEcGZGYzLurA/results request sent reply was:

String is ÿ

electronicsguy commented Feb 12, 2017

sreeramtkd commented Feb 12, 2017

sreeramtkd commented Feb 12, 2017

electronicsguy commented Mar 30, 2017

evbelda commented Apr 17, 2017

sherikapotein commented Jun 4, 2017 • edited Loading

AbdelsalamHaa commented Jan 27, 2018

sreeramtkd commented Feb 13, 2018

AbdelsalamHaa commented Feb 24, 2018

Craig1516 commented Mar 7, 2018

edugargon commented Feb 5, 2019

electronicsguy commented Feb 8, 2019

edugargon commented Feb 9, 2019

klslowik commented May 12, 2020

JiriBilek commented May 12, 2020 • edited Loading

sreeramtkd commented Feb 12, 2017 •

edited

Loading

connecting to Sree
..............
WiFi connected
IP address:
192.168.1.4
connecting to api.apifier.com
Certificate matches
requesting URL: /v1/execs/To5wxSEcGZGYzLurA/results
request sent
reply was:

String is
ÿ

sherikapotein commented Jun 4, 2017 •

edited

Loading

JiriBilek commented May 12, 2020 •

edited

Loading