H5K Posted December 19, 2021 Posted December 19, 2021 Hi, I followed this guide but despite following the steps and doing them over 3 times, I am getting this error: There appears to be a problem with your Amazon (dkrbucket3) file storage settings which can cause problems with uploads. After attempting to upload a file to the directory, the URL to the file is returning a HTTP 400 error. Update your settings and then check and see if the problem has been resolved  Anyone have any ideas?
Marc Posted December 20, 2021 Posted December 20, 2021 Could I please confirm this is the standard Amazon storage method, and not an alternative? H5K 1
H5K Posted December 20, 2021 Author Posted December 20, 2021 4 hours ago, Marc Stridgen said: Could I please confirm this is the standard Amazon storage method, and not an alternative? Correct. Although I have to say I've also tried Wasabi and I am getting a "failed to connect" error. I thought it could be some firewall issue so I disabled CSF but it's still not working.
Marc Posted December 20, 2021 Posted December 20, 2021 If it's a failed to connect issue, you need to contact your hosting company on this, as there is something blocking it somewhere
H5K Posted December 20, 2021 Author Posted December 20, 2021 48 minutes ago, Marc Stridgen said: If it's a failed to connect issue, you need to contact your hosting company on this, as there is something blocking it somewhere Amazon was HTTP Error 400, not failed to connect.. 😕
Jim M Posted December 20, 2021 Posted December 20, 2021 35 minutes ago, H5K said: Amazon was HTTP Error 400, not failed to connect.. 😕 To confirm, you are able to reach your bucket from your server? I would recommend confirming that and that all your settings are indeed correct. Something seems wrong here or is getting stripped from the request to produced this result.Â
Solution H5K Posted December 23, 2021 Author Solution Posted December 23, 2021 It ended up working. I am not sure what changed, if anything. SeNioR- 1
Marc Posted December 23, 2021 Posted December 23, 2021 Glad you managed to get it working there 🙂Â
dragonfly411 Posted February 8, 2022 Posted February 8, 2022 I had the same problem and lost quite some time debugging this. So the fix is here if someone else would be looking for it. Â
Recommended Posts