Hi,
my ESP8266 can´t connect to the Cloud Server since Wednsday, what can I do?
Is the Port correct? 443? What is the right one? I´am in Germany.
12:43:08.244 → [225704] NTP time: Fri Mar 19 11:43:07 2021
12:43:08.297 → [225705] Connecting to blynk-cloud.com:443
That for helping me
There were some issues with SSL connections to the Blynk cloud servers because of expired certificates, but I thought this had been fixed as discussed here…
Does a non-SSL connection work for you?
Pete.
Hi, Pete
what does non-SSL connection means?
How can i test that?
I tried now
13:05:53.376 → [571] Connected to WiFi
13:05:53.376 → [572] IP: 192.168.178.121
13:05:53.423 → [572]
13:05:53.423 → ___ __ __
13:05:53.477 → / _ )/ /_ _____ / /__
13:05:53.477 → / _ / / // / _ / '/
13:05:53.524 → ///_, /////_
13:05:53.577 → /__/ v0.6.1 on ESP8266
13:05:53.577 →
13:05:53.577 → [661] NTP time: Fri Mar 19 12:05:53 2021
13:05:53.624 → [691] Connecting to blynk-cloud.com:1883
13:05:58.490 → [5661] NTP time: Fri Mar 19 12:05:58 2021
13:05:58.490 → [5661] Connecting to blynk-cloud.com:1883
Presumably, your sketch currently has a line near the top which says…
#include <BlynkSimpleEsp8266_SSL.h>
Replace this with…
#include <BlynkSimpleEsp8266.h>
If your Blynk.begin or Blynk.config commands have port 443 specified then change this to port 8080
Pete.
Hi Pete,
it is works now. Thank but what was the Problem?
//#include <BlynkSimpleEsp8266_SSL.h>
#include <BlynkSimpleEsp8266.h>
#include <ESP8266WiFi.h>
…
Blynk.begin(auth, ssid, pass);
//Blynk.begin(auth, ssid, pass, “blynk-cloud.com”, 8080);
//Blynk.begin(auth, ssid, pass, IPAddress(192,168,1,100), 8080);
13:13:28.578 → [4444] Connected to WiFi
13:13:28.578 → [4445] IP: 192.168.178.121
13:13:28.625 → [4445]
13:13:28.625 → ___ __ __
13:13:28.625 → / _ )/ /_ _____ / /__
13:13:28.678 → / _ / / // / _ / '/
13:13:28.725 → ///_, /////_
13:13:28.725 → /__/ v0.6.1 on ESP8266
13:13:28.779 →
13:13:28.779 → [4524] Connecting to blynk-cloud.com:80
13:13:28.825 → [4599] Ready (ping: 14ms).
It seems like there is still a problem with certificates.
@Dmitriy are you aware of this?
Pete.
Thank you @PeterKnight for pushing on this.
1 Like