Hey there @hihihi , do you have more logs that you can provide as to why there was an error?
From your first message, you see your json had upload:0, meaning no upload was done
Your second message showed upload:1650079, meaning upload completed
For aws you should expect the same thing, success upload returns a number, failure returns 0 and sometimes no error either, just upload:0 could indicate failure
When I was trying a few times to setup AWS and had problems, I really don’t remember seeing the 500 status error when my credentials were wrong, there was a clear error message, for example when my bucket name was wrong I got a file not found response from aws, so I wonder if this error you’re having is actually related to some other change on your code.
I have the impression this 500 error is a kind of timeout, indicating the app never finished processing whatever it was doing, got frozen somehow, even typos in python code return a clear error message for example, so 500 generic error “cannot complete your request” to me generally meant the app got stuck somehow. I could be wrong but that’s why I believe it could be some other change, not just credentials.
All the times I was in this situation I was reverting small changes until things ran again, and only then started over to apply whatever changes I was doing to locate exactly where the problem was.
It took me quite a few tries to make AWS work correctly to upload and download, so what I did was to copy the storage folder from this repo into a test project separetly, create the same AWS credentials that were needed to run storage class to download and upload, so basically I “borrowed” this repo’s storage class, and made it work on a test project, and only then I figured out exactly how to setup everything.
Hope to have helped with some ideas