Invalid credentials would probably mean the payload is stripped from the call somehow... perhaps there's a FW or some load balancer in the way?

Hi Jake! The clearml.conf file content is exactly the api section that is given by our clearml server, copied using the copy button, something like

api { 
    web_server: http:// .. :8080
    api_server: http:// .. :8008
    files_server: http:// .. :8081
    credentials {
        "access_key" = "KEY"
        "secret_key"  = "SECRET"
    }
}

clearml version 1.9.0
The strange thing is that the configuration works perfectly on my machine. My coworker’s machine does have a different python (3.10) and is using windows instead of macos

Is it possible you generated them for another deployed (or SaaS) server? 😕

Hi @<1523701225533476864:profile|ObedientDolphin41> , the response seems like the credentials are wrong - can you provide some more details on the clearml.conf file you provided, and what clearml SDK version you're using?

So we got it! Still don’t understand it though.
I generated the credentials on the web ui and sent them to my coworker, they did not work at all.
He generated his own credentials and they work!

Switched off the windows defender FW, no load balancer present, still not working 😕

Still have no clue, something going wrong when reading the file due to certain encoding? Due to windows? Or maybe python?