Hi, I’ve been using the AWS File uploader from Zeroqode and has worked fine for the last year. I recently updated the plugin to a newer version and I see a lot of changed in the property UI and now I’m not able to upload any type of files.
Does anyone know what’s wrong?
I have the correct access key, secret key, region, bucket, etc
I promise, it’s very important that you regenerate your secret key… don’t know why this was flagged and not your original post given that you could be giving anyone access to your storage!
Best bet is to try an older version, and if that fails, contact @ZeroqodeSupport or ask on their forum.
Yep, I believe this means any technical user can find your API keys, and I also believe ZQ has been informed of this multiple times but decided not to do anything about it.
To the best of my understanding, API keys are secure when put in the plugin settings, not actions/front-end workflows.
Not totally secure if put in plugins settings if the plugin author have set the key “public”…
It won’t also fetch for an upload url using server side action. This is done on client side in element plugins. If Bubble could add a way to call a server side action for theses kind of plugin, this would make all of that more secure !
@segongora9, could you please share the version of the plugin you’re using and the region of your bucket? We’ve noticed some odd behaviors with specific bucket regions and want to confirm if you’re experiencing the same issue or to investigate further.
@georgecollier, let’s continue our conversation on the Wasabi forum thread to avoid duplicating information across multiple forums. We’ll respond to your latest message as soon as possible, and we also appreciate the valuable insights shared by @Jici.
For anyone concerned about this topic, you’re welcome to join the discussion in the forum linked above or if you have any other questions or concerns about the AWS plugin, please leave your message on here. Your input is always appreciated!
i was facing lot of problem with their plugin update
after having this issue with every update i just imply downgraded plugin and stayed their , just ignore their update and you will be fine
We’re sorry for this inconvenience and to hear about your experience with our plugin🙏 We’d love to learn more about the issues you’ve encountered so we can get to the bottom of it. We always encourage our users to report any weird behaviors, and we try best to provide assistance!
Please email us at support@zeroqode.com with more details about what you’re experiencing, and we’ll do our best to help