"upstream connect error or disconnect/reset before headers. reset reason: connection failure"

Rob Cecil

unread,

Mar 12, 2019, 2:30:36 PM3/12/19

to grpc.io

I did some searching and reading and could never find a conclusive answer why I am getting the message:

"upstream connect error or disconnect/reset before headers. reset reason: connection failure"

when I run my own test program.

I am running everything (grpc-node server, envoy in docker, and http server using python3) on Linux (Ubuntu Comic 18.10) and Node 11.10.0.

I merely have built a similar structure to the HelloWorld example, and copied some relevant bits (envoy.yaml, dockerfile) and combined with my own proto, client.js, and server.js.

I can call my grpc-node server successfully with a simple grpc-node client (similar to the node-client.js in the Helloworld directory on Github).

I am running Envoy using the same envoy.yaml from the hw folder, except I changed line 10 to use port 8090, since port 8080 is currently used by a system Kubernetes daemon.

my envoy.yaml:

https://gist.github.com/robcecil/0ba6c2b241c4ed986ec27940abae2550

Thanks!

Rob Cecil

unread,

Mar 12, 2019, 2:31:17 PM3/12/19

to grpc.io

Untitled.png

Rob Cecil

unread,

Mar 12, 2019, 11:26:08 PM3/12/19

to grpc.io

Found the issue:

If I start my node service with "0.0.0.0:<port>" it works great. If I specify an actual address for the server, "172.16.0.168:9090", that's when I get the error ""upstream connect error or disconnect/reset before headers. reset reason: connection failure"".

On Tuesday, March 12, 2019 at 2:30:36 PM UTC-4, Rob Cecil wrote:

Reply all

Reply to author

Forward