Hi @<1585441135088635904:profile|StoutShark79> , it seems to be the issue is related to the cookie - @<1523701827080556544:profile|JuicyFox94> any idea?
ok got it, are you able to access the system bypassing nginx with http://<Server Address>:8080
?
really weird, can you try to totally remove any cookie domain related?
Thank you for the swift response! yes, we are using docker-compose
only:
auth {
cookies {
httponly: true
secure: true
domain: ".clearml.wesort.ai"
max_age: 99999999999
}
}
moreover url exposed by nginx should be under https
Ok, let’s try to deep dive into it, what is the Helm chart version used for this deployment?
Hello, @<1523701087100473344:profile|SuccessfulKoala55> and @<1523701827080556544:profile|JuicyFox94> , thank you for your responses! And please excuse my tardiness. Currently, we are not using Helm. We chose to deploy the ClearML Server in Linux using the pre-built Docker image.
Did you applied any configuration to apiserver?
Trying to access the system with http://<Server Address>:8080 yields the same error. Also, thank you for the HTTPS tip. We will fix that!
Sorry for the delay! Removing all cookies yields the same error. Interestingly, deleting the configuration file for the API server and setting up the Clearml server again without it seems to work. We are able to access the system with both http://<Server Address>:8080
and app.clearml.wesort.ai . However, when we set up the clearml server with the configuration file again, we return to encountering the error.