You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Nomad should distinguish the error returned from the check and the failed check.
In my case the check even did not run (server was not reached, though it function well).
From the inside nginx container I ran:
@EugenKon I'm not really sure it'd be meaningful to report TLS errors for http health checks. But in any case this is clearly an issue with Consul. Consul is sending the health check requests, recording them in state, and reporting them in its UI. Nomad just registers the check. Moving this issue to the Consul repo.
Nomad version
Operating system and Environment details
Issue
If the service.check configured to check https without
tls_server_name
:and the certificate on the Nginx site does not support SAN
wi-nginx.service.internal
then there is no way to see why the check fails.Reproduction steps
See the config above.
Expected Result
Nomad should log somewhere if the check fails.
Actual Result
I can not find any error messages regarding HTTPS check.
Also this is strange to see the raw IP address when
tls_server_name
was configured:When this request actually fails:
Proposition
Nomad should distinguish the error returned from the check and the failed check.
In my case the check even did not run (server was not reached, though it function well).
From the inside
nginx
container I ran:From here we can see that the request failed. Nginx does not have any errors in its
/var/log/nginx/error.log
file.The text was updated successfully, but these errors were encountered: