The solution is to make sure the ClearML SDK (using
clearml.conf ) uses the actualy externally exposed address for the
files_server so that registered images URL is constructed in a way that will allow externally-run UI to view the images.
Hi MortifiedDove27 ,
The image URLs are actually encoded by the ClearML SDK when uploading the images, so your issue is probably the
clearml.conf configuration file - when the ClearML SDK rune, it takes the
files_server value and uses it to both upload the images, and create the URLs (which are later used by the UI).
I assume in your case, the ClearML SDK is running with
files_server: http://172.x.x.x:8081 so the URLs that you get use this value, while the file server is exposed externally with https://25.x.x.x which is why you can get there when manually replacing the links