I suspect that you're accessing the endpoint remotely. For security reasons — the endpoint is only bound to the local-loop interface (localhost/ 127.0.0.1). So you'll have to invoke with `localhost/127.0.0.1` instead of whatever host/ip you're using.
If you'd like to bind this to a different IP or all IPs on the machine, for external use by an external LB, or monitoring tool, for example — then you probably need to go through this documentation <https://docs.gocd.org/18.3.0/advanced_usage/agent-health-check-api.html>. If you're seeing some other issues — then you probably need to provide a few steps on how one can go about reproducing the issue. On Fri, Apr 6, 2018 at 8:40 PM Paul Ryan <paul.r...@stepupsoftware.co.uk> wrote: > I have a server and agent running v18.2.0. Running the Agent Health > endpoint as documented in the GoCD API Reference > <https://api.gocd.org/current/#agent-health> returns a 404. Other API > endpoints and my pipelines are all running fine. I have tried both > > `/health/v1/isConnectedToServer` and `/health/latest/isConnectedToServer' > as detailed in the reference. > > If anyone has got this to work, some tips would be much appreciated. > > > disclaimer <http://www.stepupsoftware.co.uk/emaildisclaimer> > > -- > You received this message because you are subscribed to the Google Groups > "go-cd" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to go-cd+unsubscr...@googlegroups.com. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "go-cd" group. To unsubscribe from this group and stop receiving emails from it, send an email to go-cd+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
