Thank you Martin for your fast response! Will do

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

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

(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)

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

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

SuccessfulKoala55 in step 1. it isn't written

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

Ctrl-F5

?

using Ctrl-F5 it redirects to the ClearML new login

it will switch to the new one

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

when running the docker ps command the output is empty

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

meaning the browser or in the server?

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

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

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

alright, cracking knuckles and... dive into the deep end

thank you Jake

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

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

now it's working!

thank you Jake for the assistance!

no, I meant to change the way it is reported. I'm still interested in the train_loss graph, naturally 🙂 but obviously it is reporting something that is the inverse of the train_loss, since in the graph it is exploding, and in reality (as reported in the terminal) it is decaying to 9e-2

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

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'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?

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

here is the result on the Tboard in Trains: