when running the docker ps command the output is empty

if I add :8080/login I get the new "clearML" welcome page

yes, that solved the errors, however the two lines "could not detect iteration reporting" and "reporting detected" a few moments later, still show up

I will try and let you know in the next experiment

SuccessfulKoala55 in step 1. it isn't written

Thanks Jake for your help, it's highly appreciated. This is an AWS EC2 running the clearml-server AMI (region of EC2 is us-east-1)

How do I check that? I did nothing in the settings other than the recommended defaults in the docs

(checking now, there are no Load Balancers in this region)

What's interesting is that SOMETIMES (rarely) it succeeds

can this give us a clue? I'm getting this error:

this is what I got:
{"meta":{"id":"7cd78b67e5384e739b9aec6cdc030e6d","trx":"7cd78b67e5384e739b9aec6cdc030e6d","endpoint":{"name":"projects.delete","requested_version":"2.20","actual_version":"1.0"},"result_code":400,"result_subcode":12,"result_msg":"Validation error (error for field 'project'. field is required!)","error_stack":null,"error_data":{}},"data":{}}

the "Payload" tab contains the project id info, so it shouldn't be the cause for the delete call fail

Good morning Alon, since you helped me so much getting tensorboard to show results yesterday, I'm hoping you can help me understand why some results I'm getting are strange:

So it means the old WebApp is still in cache...

meaning the browser or in the server?

I see, I'll try to clear the cache

Turns out the step I missed (maybe should be mentioned in the doc...) the configuration of the Security Group for the EC2 machine to allow inbound connections to the ports 8080, 8008, 8081, and to limit the source to my ip (or my office ip) only

tried both with Firefox and Chrome, results are similar also between computers and OS (ubuntu and Windows)

this is an error during training that points out to ElasticSearch error. This might be also the cause of the delete error, what do you think SuccessfulKoala55 ?

Thank you Martin for your fast response! Will do

thank you Jake for the assistance!

so, inbound rules should allow custom TCP for the three ports, 8080, 8001, 8081? what about the outbound rules?

ok, so now I'm able to see the website, but the gui isn't showing up:

sorry, my bad 😛 I accidentally entered into the inbound rules the port 8001 instead of 8008

now it's working!

thank you Jake

I did not... 😞 I'm a bit of a newb to the EC2