Skip to content
This repository has been archived by the owner on Oct 22, 2021. It is now read-only.

[macOS]can't load ip 151.101.228.133:443 #982

Closed
mickey518 opened this issue Dec 22, 2020 · 13 comments
Closed

[macOS]can't load ip 151.101.228.133:443 #982

mickey518 opened this issue Dec 22, 2020 · 13 comments
Labels
investigation Base triage label for bug reports.

Comments

@mickey518
Copy link

mickey518 commented Dec 22, 2020

[macOS]

download from brew

Error: connect ECONNRESET 151.101.228.133:443

@mickey518 mickey518 added the investigation Base triage label for bug reports. label Dec 22, 2020
@yegetables
Copy link

[linux]
i also have this problem

@hxhlb
Copy link

hxhlb commented Dec 30, 2020

me too!

Ubuntu 20.04.1 LTS
✖ error Error: connect ECONNREFUSED 127.0.0.1:443: Uncaught Error: connect ECONNREFUSED 127.0.0.1:443
⬤ debug at events.js 287:7

I checked the source code, it looks like a node's problem.

@wyfang
Copy link

wyfang commented Dec 30, 2020

[macos]
I also have this problem

@wrac4242
Copy link
Contributor

may i ask which version you are on?

@hxhlb
Copy link

hxhlb commented Dec 30, 2020

My environment:

Ubuntu 20.04.1 LTS
node version: 14.15.3
npm version: 6.14.10
yarn version: 1.22.5
eDEX-UI v2.2.5, download from release page, eDEX-UI-Linux-x86_64.AppImage

@chengs2035
Copy link

so how to fix it?

@ruoduan-hub
Copy link

image

I am like this, how to solve it?

@wrac4242
Copy link
Contributor

can someone try building from source, to see if the issue is with the app image

@Glonee
Copy link

Glonee commented Dec 30, 2020

same problem

@GitSquared
Copy link
Owner

I think this comes from here:

let sockHost = opts.host || "127.0.0.1";
let sockPort = this.port;
this.socket = new WebSocket("ws://"+sockHost+":"+sockPort);

...where the frontend terminal viewer is attempting to establish a websocket connection to the background TTY process.

My first instinct would be to hazard a guess about some macOS "safety/security" whatever feature blocking connections from edex (even local ones apparently... go figure why), but the :443 part of the address is unexpected. The code I linked is supposed to connect to 127.0.0.1:3000.

@wrac4242
Copy link
Contributor

0.0.0.0 is an error/invalid ip address, so something is wrong there

@wrac4242
Copy link
Contributor

can someone who is having this issue please run it from source, to rule out it being a build issue

@wrac4242 wrac4242 mentioned this issue Feb 6, 2021
7 tasks
@GitSquared
Copy link
Owner

See #1050

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
investigation Base triage label for bug reports.
Projects
None yet
Development

No branches or pull requests

9 participants