Server SSL down?

My App appears to be working - but my Raspberry Pi Node-Red, not having been touched today, has this afternoon decided no longer to connect to the server. I have only one key and it is not connecting. Any changes made today that would cause this? The Pi is working, it is connected to the outside world just as it has been since the start - but it’s not talking to your server…

In experimenting I turned off SSL - and it came back to life. I turned SSL back on - and it stopped. I’ve left SSL off for now - but it DID work with SSL???

We did new deployment today. But nothing else was changed. So SSL should work. You mean 8441 port. Right?

I assume so. Whoever did the node-red node - has a button SSL which i had set - and all worked well, but today I need to untick that to get a connection. I was just wondering if anything had changed.

Did you ever get to the bottom of this? I’ve been having exactly the same problem, but only since yesterday.

1 Like

Just remembered something… I updated the Blynk nodes in Node Red on Saturday. The version I was using before did not include the LCD node and the new one does. It seems to be only since that upgrade that I have been unable to use SSL.

guys, are you getting this error per chance in node-red ?

Assertion failed: (0), function uv_err_name, file ../deps/uv/src/uv-common.c, line 75.
Abort trap: 6

i seem to be getting that nowadays on a lot of changes, not even sure where it stems from, it seems node related more than anything…

I don’t see that anywhere in my log files…

this is quite weird, i can still connect to blynk.cc both with and without ssl
with
Node-RED version: v0.12.1
Node.js version: v0.12.0
node-red-blynk-contrib: v0.0.16
blynk-library: v0.0.23

Could you see if you’re up to dat with everything?
Cheers

hi, you might also want to try and remove node red contrib blynk and blynk library completly, and reinstall node red contrib blynk. i do believe blynk library js had some changes realted to path of ssl certs or at least the handling of them at some point in the past.

Ok. I’ll give that a try and report back…