I saw that there have been similar issues but the resolution wasn't clear. In our case, https works perfectly but the media retreival is running into 401s

It looks something like this:

.<redacted>/ClearML_POC/exp2_reporting.705a68df922d46c3848e679774faac5e/metrics/test2/test/test2_test_00000001.png?X-Amz-Date=1722509256352

Any feedback in how to solve this would be really appreciated! This is currently the only barrier in our way to adopt ClearML

Yes! This was the magic sauce! Thank you so much @<1523701087100473344:profile|SuccessfulKoala55> ! Really appreciate it

Hello @<1523701205467926528:profile|AgitatedDove14> ! The address is valid. If i just go to the files server address on my browser, i can see OK . I tried it with both, port forwarding from the service directly, as well as using a file.*.* ingress host, but no joy 😞

The network tag of dev tools shows this, but there is nothing like CORS being reported in the browser console. This link on its own does not work but the fileserver domain is working and shows an OK message

![image](https://clearml-web-assets.s3.amazonaw...

@<1523701070390366208:profile|CostlyOstrich36> @<1523701087100473344:profile|SuccessfulKoala55>