GRPC not working with https about insomnia HOT 7 OPEN

This seems to be more of a DNS problem that a TLS problem. Can you try to consume https://127.0.0.1:51811 ?

from insomnia.

I've tried that, but gave it another try

from insomnia.

any update on this?

from insomnia.

AFAIK it's atypical to use a http protocol to connect to a grpc server. Without a proxy, a regular gRPC server is expecting grpc://.

Please provide screenshots of both postman and insomnia including the request and response panes

from insomnia.

There isn't much to show, it simply works with Postman

The implementation is done by Microsoft under https://github.com/grpc/grpc-dotnet

Tried with
127.0.0.1:51811
Error: 1 CANCELLED: Call cancelled

https://127.0.0.1:51811
Error: 14 UNAVAILABLE: Name resolution failed for target dns:https://127.0.0.1:51811

grpcs://127.0.0.1:51811
Error: 14 UNAVAILABLE: No connection established. Last error: unable to verify the first certificate (2024-04-26T21:44:31.816Z)

from insomnia.

Same problem. I'm exposing a .NET Web API on 5002 (HTTP) and (5052 (HTTPS), after creating a project from the .NET GRPC service template.

HTTP works.
HTTPS doesn't.

In Postman both just works.

Setup:

HTTP response:

HTTPS response:

from insomnia.

Postman is a closed source project. So I can't compare their implementation to insomnia, if you could try grpcurl or grpcui and let us know if it works for you that would be a huge help for us to solve this for you.

@modestotech could you take a look at the .NET logs and see if this comment looks familar grpc/grpc-node#2340 (comment)

from insomnia.