Yes!

You are not cheating 😂

I'm going to ask an update to docs

In fact it's the same we are applying to helm charts for k8s

Web Server

File Server

Thanks a lot for the help debugging!

Can you pls share all 3 health checks ?

This gives me a 200 🙂

atm it’s the way to go

Just to be sure we are in sync 😁

ok, ty very much for your feedback 😄

ops

API

And I could access the web server even if the health check was failing. So that was not a problem in the end.

the goal is to get healthchecks green so ALB should be able to work

can you change the path in ALB healthcheck pls?

from / to /debug.ping

doubled copy paste

it can help debugging

Ok, I think that's been very helpful 🙂 I'll experiment a little, now that I know a Health Check that must work. I'll write here if I find something! Thanks a lot for the awesome support!

And it's still unhealthy. I am starting to suspect that somehow the Autoscaling Part in between the ALB and the ClearML server could be causing the problem.

These are the seetings for health check now

in some second it should became green

look also at the monitoring tab

JuicyFox94 I think I found the problem. To my absolute shame, the security group of the ALB had no Outbound rules, i.e. no traffic was allowed out of the ALB 🙈 . Now I can access the ClearML Webserver!

usually you can see if you are getting timeouts or wrong http code

it’s alongside health checks tab

But I still have one thing I'd like to fix: the health check for the file server on port 8081 gives me unhealthy for path "/". Is there a valid path you know I can use there for health checks? A curl gives me

Currently I'm "cheating" and counting a 405 as the success code for the healthcheck.