S3
S3 copied to clipboard
Unable to upload after upgrading from 4.1.3 to 5.1.0
Upgraded to 5.1.0 and no longer able to upload files. Tried to made changes per the README. When trying to upload a file, I get back "OPTIONS https://[bucketname].s3.amazonaws.com/ net::ERR_INSECURE_RESPONSE where [bucketname] is the bucket name I specified in the S3.config. Unless I am wrong, the URL doesn't seem to make sense as it should be something like https://s3.amazonaws.com/[bucketname].
Thanks in advance for any help!
Hmm, that makes sense. I'll check over the weekend hopefully. Unless you've been able to figure it out?
Didn't get a chance. I will try to look at it when I get some time.
Same deal here. I even used the example in this repo to rule out anything I was doing on my end. Same result.
And I agree, the URL format appears to be wrong. It definitely doesn't match what AWS gives you in their dashboard.
Have you tried forking the project and modifying that particular part? The code is very easy to read and follow ^_^. If you can make the test and let me know your findings that would really save me some time.
Okay, I think I know where the problem is. However, I have no idea how to get my Meteor app to point to my local "fork" copy. I have been trying for the last hour or so with no luck. I tried google this and I am not sure all the answers out there are still relevant with Meteor 1.0. A quick pointer as to how I can test with my local "fork" copy (with minimal pain) would be appreciated!
I tried to add this to the smart.json file and it doesn't seem to do anything:
{
"packages": {
"accounts-ui-bootstrap-3": {},
"bootstrap-3": {},
"lepozepo:s3": {
"path": "~/Projects/3party/S3"
}
}
}
You should be able to drag and drop the folder to your packages folder inside the .meteor project
Okay, I submitted a pull request.
Sweet! I'll have a look tonight after work :)
Is this fixed, i am facing the same issue. Unable to upload files, below CORS error in browser console. XMLHttpRequest cannot load https://s3.amazonaws.com/erecaho. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://localhost:3000' is therefore not allowed access