BLYNK
HOME       📲 GETTING STARTED       📗 DOCS       ❓HELP CENTER       👉 SKETCH BUILDER

ESP8266 invalid auth token

• Hardware model: ESP8266, Lolind D1 mini

  • communication type: Wifi SSL
    • Blynk server
    • 0.6.1 and 1.0.0 beta

No HW or code update was since last July.

The token was working since a year without any issue, however is offline since 17.03.2021. I’ve just started to debug, here is my log:
[192485] Current time: Fri Mar 26 17:18:19 2021
[192485] Connecting to blynk.cloud:443
[193421] <[1D|00|01|00] *******************************bf9c
[193460] >[00|00|01|00|09]
[193460] Invalid auth token

I’ve another project with ESP32, which is still online and working properly. Was there any change on 17.Mar, which can cause this broker auth token?

Thanks in advance!

Hello. Do you test Blynk Beta?

I’ve just refresh the library (Arduino offered as new to refresh), but the result is the same. :frowning:

This host is for the new Blynk cloud.

Our certificates were expired, so SSL connections are broken now. We haven’t fix that yet.

Oh, OK.
As a workaround I’ve changed:

//#include <BlynkSimpleEsp8266_SSL.h>
#include <BlynkSimpleEsp8266.h>

However looks like the SSL is not the rootcause. (My ESP32 running properly by SSL as well).

    ___  __          __
   / _ )/ /_ _____  / /__
  / _  / / // / _ \/  '_/
 /____/_/\_, /_//_/_/\_\
        /___/ v1.0.0-beta.1 on ESP8266

[4567] Connecting to blynk.cloud:80
[4622] <[1D|00|01|00] ****************************************f9c
[4662] >[00|00|01|00|09]
[4662] Invalid auth token

Ok, I’ve just downgraded to 0.6.1 and removed SSL, now it’s working finally! Thanks for your suggestion!

1 Like

@andrew911 nice! glad you made it so quick. Beta1 was published by mistake. We’ll release an update with the correct host very soon.

1 Like

“invalid auth token” issue is fixed in v1.0.0-beta.3.
Note that using beta is not recommended for general public, as it is intended to be used only with the upgraded Blynk Cloud (however, most things will work as expected).