Connecting to blynk-cloud.com:443

Solved
21

This was my default before when the SSL was working.

//existing code
var Blynk = require('blynk-library');
var Gpio = require('onoff').Gpio;
var AUTH = 'xxx';
var blynk = new Blynk.Blynk(AUTH);

I also tried like you suggested but with no luck.

#!/usr/bin/env node

var Blynk = require('blynk-library');
var Gpio = require('onoff').Gpio;
var AUTH = 'xxx';
var blynk = new Blynk.Blynk(AUTH);
22

Ok. So, try this:
var blynk = new Blynk.Blynk(AUTH, options = {
connector : new Blynk.TcpClient()
});

That will force non-SSL in the library.

IDK why the library change to use TcpClient is not working for you. I’m using an RPI 2b and I’ve gone thru 4 scenarios, using original blynk.js (1) and blynk.js-with-mod (2) as shown by @PeteKnight, and my code using blynk = new Blynk.Blynk(AUTH) (a) and blynk = new Blynk.Blynk(AUTH, options = … }) (b) as shown above. My results are:
(1) + (a) uses SSL: fails
(1) + (b) uses TCP: success (blynk-cloud.com:80)
(2) + (a) uses TCP: success
(2) + (b) uses TCP: success

23

Thank you. Now its working without modding the blynk.js file in the library.

24

Hi, I know this is old, but if you happen to get this, where do you put this code,
var blynk = new Blynk.Blynk(AUTH, options = {
connector : new Blynk.TcpClient()
});
to fix the problem? I know I need to post a new thread, but this is driving me nuts, and I’ve read so many posts about the same problem - but none of them clearly explain the fix. Thanks!

25

My guess is that you are using C++ rather than NodeJs, otherwise the proceeding posts would have been self-explanatory.

blynk-cloud.com is the server for Legacy Blynk. If you’re using new Blynk IoT then the server should be blynk.cloud.

Yes, that’s a good idea, then we aren’t guessing about what hardware, library and version of Blynk you are using.

Pete.

26