Hi @<1631102016807768064:profile|ZanySealion18> , it's getting the URL since this URL is probably the URL used by the client when registering (and uploading) the dataset.

Doesn't work unfortunately 😕 Thanks either way!

Perfect, exactly what I needed, thanks!

I hacked around the solution by setting api.files_server for the agent to the public URL, but ideally I'd avoid going through reverse-proxy if there's some path_substitution equivalent for this. Thanks

It should be the same one

Additional info:
-Public URL uses HTTPS, internal traffic doesn't.
-clearml.storage fails while trying to fetch None ...

Meaning it just replaced the internal IP with the URL at some point for some reason, it doesn't exist in that form anywhere in any configs (http and public URL).

You can use the path substitution option (see here ) to make the code run by the agent will convert public URLs (i.e. with prefix None ) to internal URLs (i.e. replacing it with http://<my-ip> )

One more related question (I hope there's a similar solution), when I log images, they appear in the UI with http://<my-ip> so they are inaccessible (they should be translated to None . Is there any path_substitution variant for this scenario in the config? I can't seem to find it in the docs. Thanks!