Response closed without grpc-status (Headers only)

This happens when Envoy or grpcwebproxy timeout happens. For grpcwebproxy you can set timeout for your needs like bellow.

--server_http_max_write_timeout=3600s 
--server_http_max_read_timeout=3600s

BUT this does not resolve that connection gets closed. So you have to figure out how to reconnect when this happens.

If you are using RxJS as I do you can add retryWhen for subscription if error happens. For example, if you have code like this.something.subscribe(...) Add following logic before .subscribe

.pipe(retryWhen(errorObservable => {
  return errorObservable.pipe(
    switchMap(err => {
      if (err.statusCode == 2
        && err.statusMessage == "Response closed without grpc-status (Headers only)") {
        return of(err)
      }
      return throwError(err);
    })
  )
}))

This would reconnect automatically on receiving this error. Beware that “Response closed without grpc-status” is returned when server is down and “Response closed without grpc-status (Headers only)” is returned when server closed connection. So filtering only by statusCode (2 == Unknown) is not possible.

Complete example would be:

this.something
  .pipe(retryWhen(errorObservable => {
    return errorObservable.pipe(
      switchMap(err => {
        if (err.statusCode == 2
          && err.statusMessage == "Response closed without grpc-status (Headers only)") {
          return of(err)
        }
        return throwError(err);
      })
    )
  }))
  .subscribe(...)

Good luck!

After switching to the Contour + Envoy setup this error vanished.