Hi MinuteWalrus85 ,
From your description I'm pretty sure you didn't shut down at least parts of the old server still running. Both the fact that the 8081 port is not free, as well the fact that you can still access the WebUI after shutting down...

Hi MinuteWalrus85 .

looks like port 8081 is in use, can you check it? docker ps will output you the running dockers (with the ports)

docker ps will also show any other containers still running (old Trains Server?)

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

Before starting this upgrade, did you shut down the old Trains Server using sudo docker-compose -f /opt/trains/docker-compose.yml down ?

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

I see

(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

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

and I didn't use the

-f

switch since it wasn't in the instructions

Are you sure this was not in the instructions? I'm going over them now and I see -f everywhere. If its missing, please point me there and I'll fix it

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

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

and then if you do Ctrl-F5?

it will switch to the new one

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

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

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

meaning the browser or in the server?

In the browser

I see, I'll try to clear the cache

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