HTTPS Error

Question

HTTPS Error

tcreis opened this issue 6 years ago · 25 comments

Hi,

I would report an issue that I am having.

Some times the script can provide the lat, long and accuracy values, but often I get
Latitude: 0.0000000
Longitude: 0.0000000
Accuracy: 40000

I understand that these values are the ones used in
typedef struct {
float lat = 0;
float lon = 0;
int accuracy = 40000;
} location_t;

I have uncommented line 12 in WifiLocation.h (//#define DEBUG_WIFI_LOCATION), and when it fails to report lan, long and accuracy there is the following indication
HTTPS ERROR

Nonetheless, when the process goes well, I can see a normal HTTP post which is aligned with this API. Not sure what is causing this. Can anyone provide support to solve this issue?

What I tried so far:
I added yield() after _client.println(request); (WifiLocation.cpp line 123) -> Problem not solved.

Answer 1 · 2018-08-04T13:00:23.000Z

Hey guys,
i have exactly the same problem!
Getting the same values above like tcreis.
HTTPS Error sounds like a problem with the certificate which is provided within this package?

Maybe this needs to be refreshed?

Answer 2 · 2018-08-04T16:38:22.000Z

Are you using esp8266 or esp32? Certificate check is only mandatory on esp32. I'll do a test and let you know the result. I will update certificate signature if it has changed.

Answer 3 · 2018-08-04T19:47:14.000Z

I am using esp8266. As i mentioned i get zero degrees on both lat and long, acc is 40 :(
This happened spontanously and now its not gonna work well again.

Thank you for your help :)

Answer 4 · 2018-08-24T07:31:17.000Z

You can enable DEBUG output from library by uncommenting this.

I've noticed that Google requires to have a billing account to use Geolocation API since mid July 2018. See this. So, if you do not have a billing method linked to you account and this API all requests will be rejected.

Answer 5 · 2018-12-13T23:05:21.000Z

This still does not work, billing account included, believe the certificate needs updating again

Answer 6 · 2018-12-20T09:53:02.000Z

Still does not work.

ESP8266 (NodeMCU V3)
ArduinoIDE 1.8.5
ESP8266 core for Arduino 2.5.0 beta2
with enable DEBUG:

HTTPS error
Location request data
16 WiFi networks found
WiFi list :
[
{"macAddress":"xx:xx:xx:xx:xx:xx","signalStrength":-69,"channel":1}, 
...
]
Latitude: 0.0000000
Longitude: 0.0000000
Accuracy: 40000

I also checked on "ESP8266 core for Arduino 2.4.2" and it works correctly.
"ESP8266 core for Arduino 2.5.0" creates problems.

On ESP32 work like charm.

Answer 7 · 2019-02-26T04:23:50.000Z

I am facing the same problem

Answer 8 · 2019-04-15T18:07:36.000Z

Hello,

Is a fix in the works? Should we fall back to 2.4.2?

Answer 9 · 2019-04-19T17:09:27.000Z

I've just noticed what was the matter. Recent ESP8266 Arduino core updates has changed SSL library to BearSSL. This has a different security checks. I've just disabled Certificate check during HTTPS connection. It should work now

Answer 10 · 2019-04-21T13:23:05.000Z

Hello Germán,

The good news... Issue is resolved. Thanks for your contributions to the Arduino community!

The not so good news... ESP8266 v.2.5.0 is not as stable as v.2.4.2. I spent nearly my entire Saturday dealing with WDT resets and other problems. I finally came back to v.2.4.2. My advice is to remain at v.2.4.2, until a future (stable) release is realized.

Best Regards

Answer 11 · 2019-04-22T13:55:13.000Z

May you check if library compiles under esp8266 2.4.2? Or you are not using latest library version?

Answer 12 · 2019-04-22T15:51:32.000Z

Hello Germán,

Latest version, WifiLocation 1.2.5, does not compile under esp8266 2.4.2. See attached error log.

I'm currently using WifiLocation 1.2.3 and esp8266 2.4.2. This combination works nicely.

ErrorLog_ESP8266_242_WifiLocation_125.txt

Answer 13 · 2019-04-23T10:23:51.000Z

I'll investigate if I can make it compatible. Newer features make use of BearSSL that is only present on 2.5.0. Thanks for testing

Answer 14 · 2019-05-01T21:45:36.000Z

@Uup115 check latest commit on https://github.com/gmag11/WifiLocation/tree/dev branch. I've not tested it, but it compiles using 2.4.2. Check if it works.

Answer 15 · 2019-05-03T04:57:12.000Z

Hello Germán,

Sorry, I've been busy this week. I'll check it on Saturday and let you know. Thanks!

Answer 16 · 2019-05-05T17:11:25.000Z

Hello Germán,

With the latest commit, WifiLocation-dev, compilation fails using esp8266 2.4.2. See attached error log.
ErrorLog_ESP8266_242_WifiLocation_125_05-05-2019.txt

Answer 17 · 2019-08-23T22:01:28.000Z

Hello Germán,

With the latest commit, WifiLocation-dev, compilation fails using esp8266 2.4.2. See attached error log.
ErrorLog_ESP8266_242_WifiLocation_125_05-05-2019.txt

Hi Germán, nice code!
I am having the very same error with cert . Any idea on how to solve?
going back to v 5.x resolves the issue.
Thanks!

Answer 18 · 2019-09-23T05:13:32.000Z

I've found the reason of compile error. I was checking if bearssl.h was present to decide if using it or axTLS instead. The problem was that code 2.4.2 already implements bearSSL, although WiFiClientSecure class uses axTLS.

I've not found any definition that allows me to identify what core version is used, so I had to add a define into WifiLocation.h in dev branch.

It is on line 13. In order to compile with core < 2.5.0 this line should be uncommented.

If you know about a way to identify core version with preprocessor let me know, please.

Answer 19 · 2019-10-01T08:42:22.000Z

I close this issue. Feel free to open it again

Answer 20 · 2021-04-12T19:44:42.000Z

It seems like this is a bug with the ESP32. If you use the HTTPClient library in the Arduino_ESP core, you can successfully send a POST request without needing additional certificates.

Example:

WiFi.mode(WIFI_MODE_STA); // Set up device as WiFi station to find other devices
  WiFi.begin(ssid, pass);
  Serial.print("Attempting to connect to WPA SSID: ");
  Serial.println(ssid);
  while (WiFi.status() != WL_CONNECTED) {
      // wait 5 seconds for connection:
      Serial.print("Status = ");
      Serial.println(WiFi.status());
      delay(600);
  }
  String body = "{\"wifiAccessPoints\":" + getSurroundingWiFiJson() + "}";

  #ifdef SERIAL_DEBUGGING
  Serial.println(body);
  #endif
  
  // Send POST request to Google Service
  HTTPClient goog;
  String googlePath = "https://www.googleapis.com/geolocation/v1/geolocate?key=" + googleApiKey;
  
  goog.begin(googlePath);
  goog.addHeader("Content-Type","application/json", false, false);
  int httpResp = goog.POST(body);
  String payload = "Empty";
  
  if (httpResp > 0) {
    Serial.print("HTTP Response code: ");
    Serial.println(httpResp);
    payload = goog.getString();
  }
  else {
    Serial.print("POST Error code: ");
    Serial.println(httpResp);
  }
  goog.end();

From here you need to parse the JSON to get your values from the response. A disadvantage of this method is that is it not thread safe like the current implementation.

Answer 21 · 2021-08-10T20:04:06.000Z

Hello everyone.
I had already made a geolocation code with this library, but for 2 days it no longer responds with the positioning or in other words I get the following error:
Location: 0.0000000,0.0000000 Accuracy: 40000 Result: API connection error
What should be done? Is there a problem with the certificate or in any case, would it be for another reason?
I will be attentive to your responses and comments.

Answer 22 · 2021-09-04T18:21:00.000Z

Hello, I have tried to use the Wifilocation 1.2.9 library with an esp32, in the library I see that the certificate in the SCR folder is different from the certificate in the .cpp file. Can you explain to me how to make the library work correctly in esp32?

Location request data
[{"macAddress": "08: 3E: 0C: 81: B0: D0", "signalStrength": - 65, "channel": 8},
{"macAddress": "BC: 3E: 07: F6: 69: 98", "signalStrength": - 87, "channel": 6},
{"macAddress": "94: BF: 95: 6D: 57: 94", "signalStrength": - 92, "channel": 8},
{"macAddress": "20: AA: 4B: 60: CF: 61", "signalStrength": - 92, "channel": 11}]

Location: 0.0000000,0.0000000
Accuracy: 40000
Result: OK
Waiting for NTP time sync:
Current time: Sat Sep 4 18:18:27 2021

Answer 23 · 2021-09-04T21:52:15.000Z

@alejolopez03 I explained how to get current certificate in https://github.com/gmag11/WifiLocation#description.

You may check #18 and #19 too

Answer 24 · 2021-09-05T06:16:36.000Z

@gmag11

I already changed the certificates, and in one I get

Result: API connection error

and with the other

I get the following:

Connected
Waiting for NTP time sync: .
Current time: Sun Sep 5 06:05:27 2021
Location request data
[{"macAddress":"24:2E:02:01:F0:99","signalStrength":-68,"channel":6},
{"macAddress":"08:3E:0C:81:B0:D0","signalStrength":-69,"channel":8},
{"macAddress":"A4:98:13:7E:E0:AF","signalStrength":-95,"channel":11}]

Location: 0.0000000,0.0000000
Accuracy: 40000
Result: OK

NOTE: I am using version 1.2.9 of WifiLocation and ESP32

Answer 25 · 2021-09-05T06:23:32.000Z

I already solved my problem, "I did not have a billing account associated with the API project"

Connected
Waiting for NTP time sync: .
Current time: Sun Sep 5 06:22:12 2021
Location request data
[{"macAddress":"08:3E:0C:81:B0:D0","signalStrength":-84,"channel":8}]

Location: 4.5383682,-75.6908035
Accuracy: 3560
Result: OK

What I tried so far: I added yield() after _client.println(request); (WifiLocation.cpp line 123) -> Problem not solved.

What I tried so far:
I added yield() after _client.println(request); (WifiLocation.cpp line 123) -> Problem not solved.