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

Blynk server down - Belgium


#1

Hi,

I’m located in Belgium ald it seems the Blynk server is down. I keep getting this message when opening the app:

Is this being handled?

Thank you,
Alexander


#2

https://www.blynk.cc/status confirms their is a problem with the European server.


#3

Working on this!


#4

Now my esps reconnected, but all 3 raspbery PIs and 2 pi zeros still cant connect. Just a feedback


#5

Ok, thank you.
It seems that it’s working again over here.

Alexander


#6

From now on, I’ll check this page first. Didn’t find it this morning where I can check the servers. Thank you!

Alexander


#7

from my view the raspbery pi client still noct working yet (all 5 from my side) but the esp`s are working…

its an endless reconnecting:
Ausgabe des Befehls /usr/bin/blynk-client dXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

OnOff mode
Connecting to: blynk-cloud.com 8441
{ Error: connect ECONNREFUSED 139.59.206.133:8441
at Object.exports._errnoException (util.js:1020:11)
at exports._exceptionWithHostPort (util.js:1043:20)
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1099:14)
code: ‘ECONNREFUSED’,
errno: ‘ECONNREFUSED’,
syscall: ‘connect’,
address: ‘139.59.206.133’,
port: 8441 }
Connecting to: blynk-cloud…same again and again


#8

Shouldn’t you be using port 80 with the latest libraries?


#9

i used this configuration until today when the cloud was down, now i have this issue, so i am not change any… i dont understand what u say, because i just call the client and the response came from the client :slight_smile:
/usr/bin/blynk-client dXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX

i dont know how change the port or any, i was thinking that is an fixed code into this client (?)

So do i have update any ?
Can you give me a procedure what i should do for change the port in the client request?

so i have to update the client?
Do you know what i have to do?

thanks for your help


#10

The default hardware ports have been changed for awhile now, as have the the various Blynk client libraries also been updated over time. As Blynk updates (and/or fixes) server issues, newer changes come into play… This may be the cause of your issue :thinking:

You appear to be running WiringPi or NodeJS? Perhaps you could just update your client libraries on each RPi as that should account for the new default ports.


#11

Probably.

Save everything you have done and then do what you previously did but with the latest libraries.


#12

Ok i try first update just the libary:
sudo npm install -g blynk-library
than it says i have to update npm and i do too.

but still after running it use the old port :frowning:

OMG —

i use node js for blynk…

So is there a way for delete the old blynk installation and than i will make a new installation?

Because i only use the pi as client, i can nothing lose because its only call the client and than i use it via app project…


#13

Yes, take out the existing SD card and put in another one.


#14

haha i still use ssd anyway… so that means i cant use blynk client longer on my installation?

I start the full instalation procedure as you suggest. But i get an error at that point: sudo npm install -g onoff

but after sudo npm install -g blynk-library it says updated

but when i run the client it still connect at 8441 :frowning: so is there any oportunity to edit the libary ports byself? maybe i delete some folders? and reinstall it ?

redirect 8441 to 80 ?


#15

Do you have 5 SSD’s for the 5 Pi’s that you are using or do you have more than 5 SSD’s?

I don’t do much Pi / Blynk stuff these days so I’m not going to guess the “upgrade” procedure.

From memory aren’t the ports declared in one of the scripts?

If you have a spare SSD I would start with a fresh install of the latest libraries etc. You can always copy over the projects when you are up an running again.


#16

I have some basics here… assuming the new client install isn’t using the proper port (I use Local Server, so I don’t know) then I guess you could just as easily use the Local Server method, but point right back to the Cloud Server IP (still recommended to use port 8080 anyhow)


#17

blynk client is just for the remot controll of my servers…
for me would be the easyst way with port rules…
so i understand the old port is 8441 and the new is now 9443 ?
Or maybe i can delete the old libary in the folder install it new, because when the new libary has the correct client ports, so it must be in any cache , so if i delete all files and than install new, should be work?
what folder files i can delete any suggestions?

I just wondering that it works until today and now all stop after server down time…

Thanks


#18

What servers? Blynk servers? How do you use a Blynk client application to control a server?

9443 is for the App, not the device… the default port for all client devices is 8080 (although in some cases just the usual 80 will work)


#19

Same problem for me on pi after servers crash. Trying update blynk-library is not working for me too (stiil trying to connect through 8441 port). Kinda dont know what to do now :roll_eyes:


#20

I suspect the old ports left you connected until such time as the server was rebooted and now you need the new ports.

I am 99% certain that the ports are in a script and you should be able to edit the script. I don’t know if any other parts of the script have changed in recent months though.