Edex-ui: [Terminal socket] Uncaught error pops up at startup and socket fails to establish when using a network proxy

[davidnegreira]

When in start the app i have this error:

error [object Event]: Uncaught [object Event]
debug at /edex-ui/src/classes/terminal.class.js 111:43

My system is:
Terminal: konsole
OS: KDE neon

[unclevan]

same problem for me

[GitSquared]

Does this happen immediately on startup?

[davidnegreira]

yes on startup, I paste all log from npm start:

▶ start Starting eDEX-UI v1.0.0
ℹ info With Node 8.9.3 and Electron 2.0.13
ℹ info Renderer is Chrome 61.0.3163.100
▶ Startup Initialized timer...
ℹ info Base config dir is .config/eDEX-UI
☐ pending Loading settings file...
✔ success Settings loaded!
☐ pending Creating new terminal process on port 3000
✔ success Terminal back-end initialized!
ℹ info Creating window...
… watching Waiting for frontend connection...
✖ error [object Event]: Uncaught [object Event]
⬤ debug at src/classes/terminal.class.js 111:43
● note UpdateChecker: Could not fetch latest release from GitHub's API.
⬤ debug Error: Error: connect ETIMEDOUT 192.30.253.116:443

[GitSquared]

@davidnegreira @unclevan Do you run anything on local port 3000-3005?
Also does that error make the window crash/freeze or is it just a pop-up you can dismiss?

[Enoooch]

I got this problem too, here is my log:

...
✔ success Terminal back-end initialized!
ℹ info Creating window...
2018-11-22 10:53:11.734 Electron[23841:1192108] * WARNING: Textured window is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.
… watching Waiting for frontend connection...
☒ complete Frontend window is up!
ℹ info UpdateChecker: Running latest version.
✖ error [object Event]: Uncaught [object Event]
⬤ debug at file:///Users/enoch/Projects/edex-ui/src/classes/terminal.class.js 111:43

1. The textured window warning above, I don't know how to fix it.
2. And the error happens after window is up.

This is my interface:

1. Can not use terminal and file system.

[unclevan]

[GitSquared]

( @Enoooch The textured window warning is unrelated and will be fixed when the next electron v3 release is published & eDEX migrates to it. )

From the screenshots I can tell that the problem is that the internal websocket that connects eDEX and the actual terminal process fails to establish and drops and error.

Unfortunately the error message isn't really helpful. I'm going to try and make it output something more interesting.

[GitSquared]

Could anyone try to run this again and tell me what's the error now?

[Enoooch]

The latest version works for me, no error this time, only the warning left, thanks!

[GitSquared]

...i didnt change anything. What the hell.

[Enoooch]

...That's odd.
I am running this code in dev mode, this is my log now:

ℹ info Creating window...
2018-11-22 20:45:00.259 Electron[40481:2300690] * WARNING: Textured window is getting an implicitly transparent titlebar. This will break when linking against newer SDKs. Use NSWindow's -titlebarAppearsTransparent=YES instead.
… watching Waiting for frontend connection...
☒ complete Frontend window is up!
✔ success Connected to frontend!
◼ Startup Timer run for: 12.73s
ℹ info Resized TTY to 066 031
ℹ info Resized TTY to 103 030
ℹ info UpdateChecker: Running latest version.
● note LocationGlobe: Error parsing data from ipinfo.now.sh
⬤ debug Error: TypeError: Cannot read property 'latitude' of undefined

Terminal and filesystem are available now.

[GitSquared]

Yeah, log looks nominal, apart from that little geoip related error. Is anyone still having this?

[unclevan]

[unclevan]

When I shut down the network proxy, everything was fine...

[GitSquared]

Hoooo. @unclevan do you think your proxy might have been blocking local connections?

[davidnegreira]

When I shut down the network proxy, everything was fine...

same here, when I do:
unset http_proxy
unset https_proxy

everything works fine

[GitSquared]

Nice. Now I know what's wrong. Will fix asap.

[Fedrius]

When I shut down the network proxy, everything was fine...

I just had this same issue. It was because I had my rails dev server running on port 3000. Once I stopped the server, EDEX-UI worked again.

[GitSquared]

@Fedrius About that, you can change the port used by eDEX in the settings. See the wiki.

[GitSquared]

I've implemented a fix based on @davidnegreira's comment. On startup, the http_proxy and https_proxy env variables are disabled.

[GitSquared]

Here are some development binaries if anyone wanna test this after the Christmas parties :christmas_tree:

can't provide builds for macOS on my own, sorry

[abhiunix]

Sir, I'm still facing the same issue with the same error message.
I have also checked my port no 3000.
No other services are using this port.

[GitSquared]

@abhiunix Two things:

• Do you use a network proxy?
• Does changing eDEX's settings to use some other port (e.g 3001) fixes the issue?