Hey @<1523701087100473344:profile|SuccessfulKoala55> thanks for the reply and apologies for the delayed response. I added an nginx webserver on top of the default open-source clearml to route requests from external clients to the host machine's ports 8080, 8008, and 8081. To browse to the UI, I use my personal domain (which resolves to the machines static IP), e.g. None I've redacted it here for privacy if you don't mind.

The only port exposed to the internet is port 80 which my nginx reverse proxy is listening to. From there, I just route requests made to /api to 8008, /files to 8081, and requests to the default webserver to 8080. I hope this makes sense I'm not the best at explaining 😓 .

With this config, the SDK works fine. I'm able to upload stuff to the fileserver, access the API, all the basic features. I was more wondering if I'm missing something in the docs where I can tell the application what is being exposed, so that the ClearML credentials generate correctly. This might also cover some niche use cases where these key: value pairs need to be accessed internally by the app itself.