gRPC error: How to solve "Connection closed before server preface received"?

I deployed DgraphAlpha and DgraphZero in docker. I am connecting to Dgraph as described in the documentation.

func newClient() *dgo.Dgraph { d, err := grpc.Dial("localhost:9080", grpc.WithInsecure()) if err != nil { log.Fatal(err) } return dgo.NewDgraphClient( api.NewDgraphClient(d), )
}

And the client is created successfully, but when I try to search

txn := i.dgraphClient.NewReadOnlyTxn()
defer txn.Discard(context.Background())
dgraphQuery := "search here"
response, err := txn.Query(context.Background(), dgraphQuery)
if err != nil { // error here
}

I get an error:

rpc error: code = Unavailable desc = connection closed before server preface received

This error does not always occur, at unexpected moments, and because of this it is difficult for me to determine its root. Has anyone encountered something similar? What could be the problem?

2 Answers

Beside other transitory causes, a common cause of this error is the server running with TLS enabled and the client attempting to connect without TLS.

Make sure you correctly configured TLS options on the client:

tlsConfig := &tls.Config{ Certificates: []tls.Certificate{myCertificate}, RootCAs: myCAPool,
}
tlsOpt := grpc.WithTransportCredentials(credentials.NewTLS(tlsConfig))
conn, err := grpc.DialContext(ctx, "<connection_string>", tlsOpt)

Make also sure you are actually using client certificates on the client connection.

0

It may be some issue with timing. This may happens more often in the first requests? Do you have any log on the Dgraph side?

Consider:

  1. Use dial option WithBlock() to ensure you have a connection
  2. Use DialContext and use a context with timeout to avoid wait a lot
  3. Be aware that Insecure dial option is deprecated

Deprecated: use WithTransportCredentials and insecure.NewCredentials() instead.

About the error:

Status code 14

This seems a transient error.

You may retry after some time. There are some retriers that can be used on this case like:

2

Your Answer

Sign up or log in

Sign up using Google Sign up using Facebook Sign up using Email and Password

Post as a guest

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

You Might Also Like