ECONNRESET

[Nowelec]

Hi,
I have a many "reset connexions" on Gekko running in server mode below the logs :

Error: read ECONNRESET at exports._errnoException (util.js:1018:11) at TCP.onread (net.js:572:26)
Error: read ECONNRESET at exports._errnoException (util.js:1018:11) at TCP.onread (net.js:572:26)

My Config file

Uiconfig 👍

const CONFIG = {
    headless: true,
    api: {
        host: 'IP',
        port: 3000,
    },
    ui: {
        ssl: false,
        host: 'IP',

        port: 3000,
        path: '/'
    }
}

if(typeof window === 'undefined')
  module.exports = CONFIG;
else
  window.CONFIG = CONFIG;

Thanks in advance for your help
Regards
NL

[askmike]

These errors might also come from Gekko talking to exchanges, some questions:

• what were you doing when those errors occured? (importing, running live gekko, etc)
• did you install gekko on your own computer, or is it running external and are you connecting to it via the network?

[askmike]

also: is something actually not working or are you worried about those errors?

[Nowelec]

Yes it occurs directly when I try to connect on to Gekko service by the Internet side.
But in LAN mode it seems to work perfectly no connexions RESET.
So I can't share my Gekko onto the Internet Network.
It is a quite big trouble for me.
I try to put a Apache reverse-proxy (mod_proxy_http), the problem remains.
Thanks in advance for your help.

Best Regards.
NL

[askmike]

Yes it occurs directly when I try to connect on to Gekko service by the Internet side.

What do you see in your browser? Do you see any part of the website?

I try to put a Apache reverse-proxy (mod_proxy_http)

Apache will be hard since Gekko also uses websockets, which are not supported by apache. You can try nginx instead, here are instructions on how to set up nginx instead.

[Nowelec]

Thanks a lot for your response.
Yes I can see the home page but after a have immediatly a disconnected message.
I try to refresh the browser but the message of disconnexions remains.
Without reverse-proxy the issue is the same.
That's why I tried to put a reverse-proxy to help Gekko to handle this.
I don't understand why all the local connexions work perfectly !
For the moment I have no firewall activated on this server for the tests.
Thanks in advance for your help.

Best Regards.
NL

[askmike]

This error message means Gekko is unable to setup a websocket connection between gekko and your browser. Are you able to connect to other websites that use websockets? Also: did you configure the UIconfig correctly? Read more about how to do that here: https://gekko.wizb.it/docs/installation/installing_gekko_on_a_server.html#Configuring-Gekko-to-run-headless-in-a-trusted-environment

…

On Tue, Apr 25, 2017 at 9:58 PM, Nowelec ***@***.***> wrote: Thanks a lots for your response. Yes I can see the home page but after a have immediatly a disconnected message. I try to refresh the browser but the message of disconnexions remains. Without reverse-proxy the issue is the same. That's why I tried to put a reverse-proxy to help Gekko to handle this. I don't understand why all the local connexions work perfectly ! For the moment I have no firewall activated on this server for the tests. Thanks in advance for your help. Best Regards. NL — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#710 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA7MD1GpWi-31wYTFofx5VGh3wyXu-AUks5rzl5_gaJpZM4NFXLO> .

-- PGP key at keybase.io/mikevanrossum <https://keybase.io/mikevanrossum/key.asc>

[Nowelec]

I have again "connexions resets" on my browser now errors in nginx logs below 👎

2017/04/26 01:36:57 [error] 5000#0: *64 connect() failed (111: Connection refused) while connecting to upstream, client: 123.123.123.123, server: , request: "GET /assets/furtive.min.css HTTP/1.1", upstream: "http://[::1]:5000/assets/furtive.min.css", host: "18.18.18.18", referrer: "https://18.18.18.18/"

2017/04/26 01:37:08 [error] 5000#0: *79 connect() failed (111: Connection refused) while connecting to upstream, client: 123.123.123.123, server: , request: "GET /api/gekkos HTTP/1.1", upstream: "http://[::1]:5000/api/gekkos", host: "18.18.18.18", referrer: "https://18.18.18.18/"

I think Nginx try to connect to nodjs on the IPv6 loopback [::1] and nodejs is just listening on IPv4.

Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:5000 0.0.0.0:* LISTEN 4905/node
instead
tcp6 0 0 ::1:5000 :::* LISTEN XXXX/node

[Nowelec]

How can I manage this problem I saw some blogs but nothing seems to work.
Thanks in advance for your help.
Best regards
NL

[askmike]

Sorry for the delayed response!

Ah, on default the server did not listen to IPv6. I just pushed a commit to the develop branch that forces the server to listen to IPv4 as well as IPv6. Could you download the develop branch test if it works @Nowelec ?

[Nowelec]

Hi Askmike,
Great job no more reset connexion !!!
Thanks for your help.
Best regards
NL