Hi MinuteWalrus85 , sorry, missed this 😞
The error you're showing seems to indicate the WebApp sent a request with no "project" field, which is very strange.
Can you look at the request info for that specific call and share the JSON sent by the WebApp to the server (for which what you've was the response)?

Hi MinuteWalrus85 , can you look at the Network section in your browser's Developer Tools (F12) and see the what is reported when you try to delete? I assume one call returns with an error status

LEt me try and find what was the reason back when I saw it...

What's interesting is that SOMETIMES (rarely) it succeeds

the "Payload" tab contains the project id info, so it shouldn't be the cause for the delete call fail

OK, if that's still the error for this call when "project" is in the actual payload, we might have some proxy issue - it might be that someone is dropping the payload along the way - where/how is your server hosted?

Well, this basically means ES was non-responsive, but the error you described earlier had to do with a missing parameter when a request has reached the server, which is very different...

Any special settings on ELB? I've seen once an ELB stripping payload from HTTP GET calls and producing the same results

How do I check that? I did nothing in the settings other than the recommended defaults in the docs

(checking now, there are no Load Balancers in this region)

this is what I got:
{"meta":{"id":"7cd78b67e5384e739b9aec6cdc030e6d","trx":"7cd78b67e5384e739b9aec6cdc030e6d","endpoint":{"name":"projects.delete","requested_version":"2.20","actual_version":"1.0"},"result_code":400,"result_subcode":12,"result_msg":"Validation error (error for field 'project'. field is required!)","error_stack":null,"error_data":{}},"data":{}}

this is an error during training that points out to ElasticSearch error. This might be also the cause of the delete error, what do you think SuccessfulKoala55 ?

tried both with Firefox and Chrome, results are similar also between computers and OS (ubuntu and Windows)

Can you try checking with a different browser...?

Thanks Jake for your help, it's highly appreciated. This is an AWS EC2 running the clearml-server AMI (region of EC2 is us-east-1)

can this give us a clue? I'm getting this error: