Hi DashingKoala39 , how did you set up the SSL termination?

Hi again SuccessfulKoala55 ! I used nginx and Let's Encrypt, and used the recommended steps from the community that were posted here https://github.com/allegroai/clearml-server/issues/78

I just realized something, one thing that confused me is the docs said that you get the app/api/etc subdomains but I seem to connect directly using the http://subdomain.domain.com without http://app.subdomain.domain.com and in fact http://app.subdomain.domain.com doesn't work. Would that matter? Should I have *. http://subdomain.domain.com on my certificate and does that nginx file in the link need to be added to at all?

Oh, wait, so how did you configure the clearml.conf file? what are the values for the api server, web server and files server?

so my clearml.conf file only has settings for my google bucket, when I created the VM from the image it didn't actually come with any config files in the /opt/clearml/config directory, so I've been adding them and putting in the sections I need to edit there.

I do have this bit from the docs in my apiserver.conf files

auth { cookies { httponly: true secure: true domain: ".clearml.mydomain.com" max_age: 99999999999 } }Which I thought was the way to configure subdomains, but I didn't do the load balancer config as I don't need load balancing for our use case.

I was referring to the SDK configuration since you said you're getting the error when using the credentials from the server when running python

Oh sorry I misunderstood, I don't have any conf files for the SDK at the moment. When I tried via python I simply used the credentials I got from my instance and when I tried on the command land I ran clearml-init and followed the prompts until it ran into the same SSL error. During the prompts I got to #2iii on this page https://clear.ml/docs/latest/docs/deploying_clearml/clearml_config_for_clearml_server/ and that's when I got the SSL error so I couldn't get to the configuration of those URIs

So basically clearml-init should have created a clearml.conf file in your home for - can you find it and share its contents?

You can leave out the credentials embedded there, of course 🙂

I think maybe it didn't get far enough to do that because I see a .clearml_data.json file in my root but no clearml.conf. I could PM you the connection credentials if that might help? It isn't live yet so I don't mind, just let me know!

Can you see this file in your home folder (not root)? i.e. ls -la ~ ?

Sorry, I was in ~ I just (probably mistakenly) refer to that as root

Hi @<1523701087100473344:profile|SuccessfulKoala55> ! Any other ideas on this one? I feel like it has something to do with the api server but I really am at a loss for how to fix it

Oh, my mistake - if you ran into this issue when running clearml-init , the file wouldn't have been created...

So the question is, what exactly did you paste into the clearml-init during the process? Can you share what you received from the server in step 2ii ? (of course, you can mark out the key/secret there)

Thanks for the response! As instructed by the init file I pasted the full JSON object from the app credential screen, so it looked something like:

api { 
    web_server: domain
    api_server: domain:8008
    credentials {
        "access_key" = "xxx"
        "secret_key"  = "xxx"
    }
}

As an update, to get my team up and running I redid the server with everything except for the SSL, and it worked with no issues. But I'd still like to try to get SSL configured for obvious reasons so I appreciate the help!

    web_server: domain
    api_server: domain:8008

Did the domain start with http ? https ? Were these addresses consistent with how you configured your network?

When I was getting the SSL error, it was using https, and it should have been consistent, though I really just copied over the nginx settings from the github here None . I was playing around with it a bit because I thought maybe since other ports don't seem to be handled that was the issue but no matter what I tried I still got the same errors.