I suspect you were hitting the server that has been updated to a new rewritten version of the frontend and I think @lonvia has already deployed a fix for CORS issues in the last few hours…
I suspect you were hitting the server that has been updated to a new rewritten version of the frontend and I think @lonvia has already deployed a fix for CORS issues in the last few hours…