Ah apologies for getting the wrong end of the stick a bit!
Not sure if it helps you or not, but when the link to an artifact didn't work for me it was because the URL being used was internal to the server (I had an agent that had access to internal endpoints). In my case setting the agent fileserver url to the public domain solved my issue.
Hey, thank you for answering.
I know this issue and I have it sometimes, but my current issue is a direct result of me trying to make SSL work. So I am not asking for help in solving my problem, but only for help how to debug. Finding out which step leads to the artifact not being deleted (e.g. the fileserver cannot be reached by from wherever the delete request is send)
Thanks, I will look into it. For me the weird thing is that saving works and only deletion fails somehow.
Is that deletion when deleting a task in the GUI?
Mhhm, good hint! Unfortunetly I can see nowhere in logs when the server creates a delete request
So actually deleting from client (e.g. an dataset with clearml-data) works.
From my limited understanding of it, I think it's the client that does the saving and communicating to the fileserver not the server, whereas deletion is done by the GUI/server which I guess could have different permissions somehow?
It seems to be an issue that a few people are having problems with: https://github.com/allegroai/clearml-server/issues/112