HTTP /healthz check in Nomad GET /healthz
#1976
-
|
I'm trying to get the SpiceDB Output of What am I doing wring? HTTP seems to be enabled. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 1 reply
-
|
I also tried moving the HTTP check to the "http" service (edit: I was running a separate Docker image that was responding to the HTTP /healthz check. Can't get the Nomad job to respond on /healthz) |
Beta Was this translation helpful? Give feedback.
-
|
I can see the ports allocated correctly in the Nomad web UI, but cannot access the health check at http://127.0.0.1/healthz even though grpc-health-probe works against |
Beta Was this translation helpful? Give feedback.
-
|
I can see the SpiceDB logs in the Nomad web UI showing that HTTP server has been started at 0.0.0.0:8443 and gRPC on port 50051: |
Beta Was this translation helpful? Give feedback.

A difference I see is that the HTTP port is not listening over all interfaces, like gRPC. Note:
0.0.0.0:8443vs
:50051Not sure if that would matter in Nomad, but it's worth double-checking. You can change the HTTP address with the corresponding flag.