Manuel

I suspect proxy issues (probably an enterprise HTTP proxy that does not support HTTP/2 correctly, which is required for gRPC to work). grpcurl does not support proxies, so that's probably...

Your server reflection URL starts with `https://`, right? Could you also try something along this way? ``` set HTTP_PROXY= set HTTPS_PROXY= set ALL_PROXY= start "" "c:\program files\kreya\kreya.exe" ```

I could only find two ways to reproduce this: - By setting the environment variable `DOTNET_SYSTEM_NET_HTTP_SOCKETSHTTPHANDLER_HTTP2SUPPORT=false` - By setting `HTTP_PROXY` and `HTTPS_PROXY` to `http://example.com` (or any HTTP URL). Using `https://example.com`...

I'm really at a loss here. It may be a misconfigured HAProxy issue, but then grpcurl shouldn't work either. Could you try the Kreya importer without a certificate? Do you...

Do you have access to `curl` on your machine? Could you show the full output (domain name can be removed) from this command? ``` curl -sIv https://your-domain.com ``` Please also...

It looks like the endpoint supports HTTP/2 correctly (as indicated by `ALPN, offering h2`). Would you mind trying another theory? It may be that Kreya (or .NET rather) uses the...

Could you try `https://grpcb.in:9001` as the importer URL (without any certificate) to see whether other gRPC services work? In addition, could you try a `GET https://your-endpoint.domain/grpc.reflection.v1alpha.ServerReflection/ServerReflectionInfo` REST (not gRPC) request...

Yes, it looks like your company network/proxy is the root cause of the failure. I don't think we can do anything on our side to solve this issue

Thank you for your feature request. We plan to implement this and added it to our backlog.

Cool ideas! We plan to implement this soon(ish). Don't feel bad for creating an issue, we are very happy that we receive such detailed feature requests and that you find...