nicholasjackson/fake-service

gRPC error with nomad and consul

85humberto opened this issue · 1 comments

I was using fake-service for some weeks with no problems. Now I'm having trouble with gRPC.
I'm using nomad + consul connect. Just gRPC is failing, if I change the URI from grpc:// to http:// it works.

Here are some logs:

2022-08-22T23:31:12.739Z [INFO]  Calling upstream service: uri=http://127.0.0.1:8080 type=HTTP request="GET http://127.0.0.1:8080 HTTP/1.1
Host: 127.0.0.1:8080"
2022-08-22T23:31:12.739Z [INFO]  Calling upstream service: uri=http://127.0.0.1:8082 type=HTTP request="GET http://127.0.0.1:8082 HTTP/1.1
Host: 127.0.0.1:8082"
2022-08-22T23:31:12.743Z [INFO]  Calling upstream service: uri=grpc://127.0.0.1:8081 type=gRPC
2022-08-22T23:31:12.745Z [ERROR] Error processing upstream request: error="rpc error: code = Unknown desc = OK: HTTP status code 200; transport: received the unexpected content-type "text/plain; charset=utf-8""
2022-08-22T23:31:12.749Z [ERROR] Error handling request: error="rpc error: code = Unknown desc = OK: HTTP status code 200; transport: received the unexpected content-type "text/plain; charset=utf-8""
2022-08-22T23:31:12.749Z [INFO]  Finished handling request: duration=10.253186ms

Sorry, it was just a network issue.