Connect Econnrefused Rpi Part2

Issues and Errors
1

Excuse sir, at this link

I use Raspberry Pi 3 and still have error,
Firewall my raspi has disabled.

So, can teach me. How to fix it
Thx for helping

Connecting to: blynk-cloud.com 8441
{ Error: connect ECONNREFUSED 188. 166.206.43:8441
at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1117:14)
code: ‘ECONNREFUSED’,
errno: ‘ECONNREFUSED’,
syscall: ‘connect’,
address: ‘188.166.206.43’,
port: 8441 }

2

Did it work at one time, or has it always been broken? Can you post your top most code for use to view?

1 Like
3

I use blynk first time, when I follow instruction on any website. After
blynk-client BLYNK_AUTH

It always been broken.

chrome
Screenshot_2019-01-05-21-32-59-621_com.android.chrome.png1080×1920 214 KB

So can help me for this problem…
Thanks

4

there is a mistake in the instructions … it says "npm install npm… you want to do an “apt-get install npm”…

but, assuming you caught it during the install…
copy and paste what happens when you do a “blynk-client <authcode>”

anykind of upstream firewall in place, i know you said the pi firewall was turned off ?

1 Like
5

can you install nslookup?

apt-get install dnsutils

and run it on blynk-cloud.com?

root@raspberrypi:~# nslookup blynk-cloud.com
Server:         75.75.75.75
Address:        75.75.75.75#53

Non-authoritative answer:
Name:   blynk-cloud.com
Address: 45.55.96.146
1 Like
6

i have same problem
I didn’t change anything on my RPi, but when i start my script now, I get that message:

Connecting to: blynk-cloud.com 8441
{ Error: connect ECONNREFUSED 139.59.206.133:8441
    at Object._errnoException (util.js:1022:11)
    at _exceptionWithHostPort (util.js:1044:20)
    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1198:14)
  code: 'ECONNREFUSED',
  errno: 'ECONNREFUSED',
  syscall: 'connect',
  address: '139.59.206.133',
  port: 8441 }

I have no idea what the problem is.

Thanks for helping.

7

The new (as of last year) proper port for SSL is 9443. Recent server issues now insist upon it.

You need to confirm updated library and/or edit a line in it for the new proper port.

See this topic for details…