Heard about Koyeb on the Cup O’ Go podcast.
I’m building a gRPC health check service (https://ack.al) and have a known-working gRPC healthcheck server that implements the gRPC Health Check protocol.
I deployed the container to Koyeb and it deployed successfully, first time. I found the UI unfamiliar and initially didn’t make the container’s (default|50051
) port public.
I’m unable to gRPCurl the service’s endpoint.
The UI Dashboard shows that the app’s healthy and the app logs are expected.
I was unclear whether the service would be published under 443 or 50051 but think 443 is correct. I’m able to query the endpoint’s TLS:
openssl s_client -connect ${APP}.koyeb.app:443 2>/dev/null \
| openssl x509 -noout -dates
notBefore=Jun 1 12:10:38 2023 GMT
notAfter=Aug 30 12:10:37 2023 GMT
I’ve tried:
grpcurl \
-vv \
-connect-timeout 10 \
${APP}.koyeb.app:443 \
grpc.health.v1.Health/Check
The connection doesn’t return|timeout.
Is there any way to inspect request logs?
The service assumes the proxy will terminate TLS and expects a plaintext gRPC connection.
I was unable to find a gRPC tutorial in your docs but found e.g. End-to-end gRPC ….
Any guidance on what I’m doing wrong would be appreciated.