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

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

Thanks for letting me know, I'd be very happy to update.

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

now it's working!

thank you Jake

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:

I think you have the page cached - can you try reloading using

Ctrl-F5

?

using Ctrl-F5 it redirects to the ClearML new login

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

meaning the browser or in the server?

when running the docker ps command the output is empty

SuccessfulKoala55 in step 1. it isn't written

(and I didn't use the -f switch since it wasn't in the instructions, and I'm not familiar with dockers all that much)

Thanks Jake, clearing the Cache did the trick! thank you so much for your assistance!

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

after running docker ps I saw that all the ports are still listed. I then changed the name of /opt/clearml back to /opt/trains and ran the command sudo docker-compose -f /opt/trains/docker-compose.yml down and it did the trick

going to the server URL:8080 -> old trains login (working as usual if I enter my credentials) -> Ctrl-F5 -> switched to the new interface

I see, I'll try to clear the cache

it will switch to the new one

it turns out that my docker-compose.yml wasn't in the environment path, so when I first ran the down command, it had no effect

after upgrade - if I go to the url and ending with :8080 I get the old "trains" welcome page

but if I just enter the URL with ending :8080 it takes me to the old login

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":{}}

I'll look at the security group. Any tips on how to configure it so that it isn't exposed to the entire world, but also not locked to me?