VexedCat68 , what errors are you getting? What exactly is not working, the webserver or apiserver? Are you trying to access the server from the machine you set it up on or remotely?

VexedCat68 , can you try accessing it as
192.168.15.118:8080/login first?

I think maybe it does this because of cache or something. Maybe it keeps a record of an older login and when you restart the server, it keeps trying to use the older details maybe

when you connect to the server properly, you're able to see the dashboard like this with menu options on the side.

You can see there's no task bar on the left. basically I can't get any credentials to the server or check queues or anything.

Changing cookie name is part of server's basic configuration in the apiserver.conf file, see here https://github.com/allegroai/clearml-server/blob/a64c4d264d00eadd2d11818b37151d3cc6266d99/apiserver/config/default/apiserver.conf#L72

I feel like they need to add this in the documentation 😕

There's a whole task bar on the left in the server. I only get this page when i use the ip 0.0.0.0

wrong image. lemme upload the correct one.

Also, is clearml open source and accepting contributions or is it just a limited team working on it? Sorry for an off topic question.

VexedCat68 this likely happens since you already have a token for another ClearML server (perhaps another server you've set up?). The correct fix it to either make sure you clear your browser's cookies, or (if you have more than one server set up), make sure each server uses a different cookie name.

I've been having this issue for a while now :((

Ok this worked. Thank you.

Shouldn't I get redirected to the login page if i'm not logged in instead of the dashboard? 😞

let me check

When I try to access the server with the IP I set as CLEARML_HOST_IP, it looks like this. I set that IP to the ip assigned to me by the network

Big thank you though.

I think I get what you're saying yeah. I don't know how I would give each server a different cookie name. I can see this problem being resolved by clearing cookies or manually entering /login at the end of the url

VexedCat68 , It appears to be a bug of sorts, we'll sort it out 🙂