still having issue. is it possible that there some issue in setting up wasabi bucket like policies or somthing.
Hey @miracle,
Good news! We’ve addressed the issue with the “File’s(Wasabi) Preview” state and have deployed an update. To benefit from this fix, kindly update the plugin to version 1.94 within your app, and you should find that the preview of uploaded files operates as before.
Your feedback was invaluable, and we deeply appreciate it. While we strive for excellence in our products, there are instances when bugs might slip through. 
Do give the updated version a spin and share your experience. If you need any additional information or assistance, we’re here to help.
Warm regards,
Zeroqode Support Team.
1 Like
Hey @AAL,
Thank you for your reply.
We have confirmed with our dev team, and they have verified that this URL is the endpoint for our Lambda service on AWS. This service hosts the plugin’s code, essentially serving as a function that handles the plugin’s backend actions.
Indeed, in an ideal design, sensitive credentials like AWS keys should never be exposed to third-party services directly.
Find more information about Uploading files to Wasabi from another cloud here: https://docs.zeroqode.com/plugins/wasabi-cloud-storage#e551c1e180e3455ca10bb09b0e546514
Hope this helps.
All the best, 
Hi @mahad.haqqi,
Thank you for your reply.
For successful integration of the wasabi Plugin inside your Bubble app, we recommend you carefully check the Supporting documentation, step-by-step, and also refer to the demo editor page for workflow examples.
Should you require additional details, please let us know.
Best regards, 
Zeroqode Support Team.
Hello @ZeroqodeSupport , thank you for the plugin. I’ve purchased it and have been testing it for a while now. I’m relatively new to this, so I’m in need of some guidance. I’m experiencing difficulty in viewing the uploaded PDF on my Bubble app.
I’ve also tried opening it by pasting the URL into a web browser, but it states that the file isn’t public. I’ve already configured the file to be public and implemented the ‘Restrict access to the bucket (deny access to all except the application visitors)’ policy.
Another question is, I wanted to add the names and URLs of the last uploaded files to the database. However, based on the preferences shown in the image below, the saved file name and URL are from the previous file uploaded, not the one I just uploaded. So it is not updated in real-time.
Pardon my novice questions, could you please help me identify what I might have done incorrectly?
Thank you so much in advance
Hi @apeL,
Thank you for your message and purchase.
In order to successfully integrate the plugin into your Bubble app, we recommend to check carefully the plugin’s supporting documentation.
How to Setup: https://docs.zeroqode.com/plugins/wasabi-cloud-storage#6109c844316649ccb4d8ec0b24573ab6
Please make sure you’ve set a Payment method. While you do receive a month free trial to upload private files, a paid account is required to upload public files.
Once you’ve obtained all the API keys and inserted them in the plugin tab, please see the plugin demo page for additional guidance: https://appkit.bubbleapps.io/wasabi?debug_mode=true
You can Generate a pre-signed URL for the uploaded file, see an example below:
Here you can find some useful Use Cases and how to implement them.
Also, you can view this tutorial Video of how to integrate the plugin.
Hope it helps.
Let us know in case you need any further information.
Best regards,
Zeroqode Suport Team.
https://knowledgebase.wasabi.com/hc/en-us/articles/13615396482203
starting from March 13, 2023, Wasabi will alter its default security settings for customers who desire to create public buckets and objects. For newly created accounts, any buckets created after this date cannot be enabled for public access by the user via the console or CLI.
Previously, buckets were always private by default, and trial accounts were unable to set their objects or buckets as public without prior request to support@wasabi.com. For the majority of Wasabi use cases, public access is not required, and thus, no action is needed for most customers. We recommend that you make use of other options such as pre-signed URL’s in order to share your documents (see How do I generate pre-signed URLs for temporary access with Wasabi?).
If, however, you have use cases that require public bucket access you may contact Wasabi support to request to enable the feature.
If you have any questions or concerns, feel free to contact Wasabi Support.
Sincerely,
Wasabi Technologies
Plugin developers are likely using old buckets which is why they can’t recreate this new issue.
I’ve only been at this for a few hours but the only way I can get an image to display in my app is by Generating a presigned URL.
I can’t get the download a file working.
I can retrieve files, generate presigned urls and download them with an html element but that’s a bit of a hassle.
Here’s my code for creating a download button in a repeating group of presigned links if anyone is interested.
<button id="downloadButton">Download Image</button>
<script>
async function downloadImage() {
const imageUrl = 'Current cell's text';
const response = await fetch(imageUrl);
const blob = await response.blob();
const link = document.createElement('a');
link.href = URL.createObjectURL(blob);
link.download = 'rectangle.png';
document.body.appendChild(link);
link.click();
document.body.removeChild(link);
}
document.getElementById('downloadButton').addEventListener('click', downloadImage);
</script>Not sure if it is meant to work like this, I just updated to the latest version of this plug-in.
My access key and secret key were blank, and it exposed the need to enter that information in each instance of the Wasabi element. And all my Wasabi elements gave an initialize error.
Older Version with keys:
Update and Keys gone and nothing works:
New Spot for Keys?
Is this an intended consequence of the new versions? Did I miss something?
The plug-in documentation still refers to the original location for the keys.
1 Like
Hi @dschmid00, @ratsoundsystems,
Thank you for using the Wasabi Cloud Storage Plugin.
Our dev team has adapted the plugin to Node18 and released some Beta features to the live version.
Please bear with us while we investigate and fix everything. We will get back to you shortly with an announcement. 
Appreciate your understanding. 
Best regards,
Zeroqode Support Team.
Hello @ratsoundsystems and @dschmid00,
We hope you had a great weekend.
We are happy to report that we have effectively resolved the issue with the Wasabi Cloud Storage plugin action and updated it to version 1.97.0.
Could you please update the plugin in your application to this latest version and confirm if everything is working smoothly now?
Also, we would like to inform you that in the new version of the plugin, you need to insert API keys in the plugin element, along with the plugin tab, as indicated in the screenshots below
This was done to improve the plugin security over the web and prevent other users from seeing personal API keys in the browser console.
Feel free to explore the functionality of the plugin on our demo page.
We really appreciate your patience and cooperation in this process.
Сheers!
@ZeroqodeSupport I’m very surprised to see access key and secret key on the element itself. Can you please confirm that this is both correct and secure? I haven’t seen this with any other plugins. Also, since these aren’t dynamic fields, I’m having to use a conditional to specify my dev and live keys which I also don’t love. Thoughts?
Also, it seems like the ‘Files count’ state on the wasabi element isn’t populating until the upload is complete. Previously it populated when the files were selected and stayed populated throughout the upload. Can we fix this issue?
Hello @avern87,
Thank you for reaching out to us!
Regarding the visibility of keys in the plugin settings, we have observed instances where the keys inserted in the plugin settings become visible in the console. However, having the keys in the actions or elements should not expose them in the console. Please note that if you have the debug mode active for your live page, the keys could potentially be visible in the debugger.
As for the “File Count” state returning information only after uploading a file, I will create an investigation report for our developers to examine this issue. We will assess the feasibility of implementing a solution in a future update. I will keep you updated with any information we gather.
Thank you for bringing these concerns to our attention. If you have any additional questions or encounter further issues, please don’t hesitate to reach out to us either directly at support@zeroqode.com or here on the forum.
Wishing you a productive Monday! 
Thanks for the reply!
Any sense of an eta to fix the file count bug?
Also, the plugin is currently throwing errors like crazy at the moment. Even at pageload before I’ve interacted with it. Can you help?
Hello @avern87,
To better assist you with the error message you’ve encountered, could you kindly provide us with the settings of the Wasabi element? We’d like to replicate the scenario to understand where the error is originating from and provide a more accurate solution.
Thank you for your cooperation, and we look forward to resolving this issue for you.
Wishing you a great day
Thanks for the reply! I’m actually seeing the console errors even if I throw a brand new element on a newly created empty page. It throws 2 errors even though there’s only one element on the blank page. There are several things you have to do to resolve issues related to a new element on a blank page. To resolve, I did the following (All unmentioned settings are left on default, out of the box values):
- Entered key and secret
- Set data types
- Set a bucket name
- Set a region
Hello @avern87
Thank you for the provided details!
We’ve attempted to recreate the problem by placing a Wasabi element on a new page without setting up any fields, but we didn’t encounter any errors in the console. In order to better understand the issue, we kindly request that you share a screen recording using a tool like Loom or your preferred software. This will help us see exactly how the element is set up and the errors you’re experiencing. We apologize for any inconvenience this may cause, but your cooperation will greatly assist us in diagnosing and resolving the problem.
Regarding the “file count” state, we conducted further tests and found that the plugin is indeed functioning as expected. The state updates correctly without requiring file uploads first. If you could also include this part in the screen recording, it would be very helpful for us to pinpoint any potential issues on your end.
Thank you for your assistance, and we look forward to your reply
Cheers!
Hello Again Zerocode;
I have not updated yet, I am still on 1.9.0, as I do not want to go through and update each individual wasabi element with the api keys yet.
But, this has changed from a week ago it seems, I can upload one file successfully, , and then the second time I try to upload a file using the same uploader, I get this error?
This is occurring on file upload actions I have not touched in over a year, not just new stuff I am working on.
Hi @ratsoundsystems,
Could you please update the plugin to a version below 1.97.0 and let us know if you are still encountering the error? In version 1.97.0 and beyond, the keys will need to be inserted directly into the element itself. Therefore, as you mentioned, “I do not want to go through and update each individual Wasabi element with the API keys yet.”, to troubleshoot the error you’re experiencing, please upgrade the plugin to a version below 1.97.0.
We understand your hesitation to update each individual Wasabi element with the API keys, but unfortunately, we cannot address the error message without upgrading the plugin.
We’ll be here to assist you once you’ve had a chance to update the plugin. Please don’t hesitate to reach out if you have any further questions or concerns.
Wishing you an amazing Friday
ok @ZeroqodeSupport
I updated to plug-in version 1.97.0 and copied all of my keys to the individual instances of the Wasabi Element.
Now I get the following errors as soon as the Elements are visible/become initialized.
These are occurring on all my Wasabi instances, most of which have been in use for a few years.
It does appear it is now functioning properly, but of course the error is not desirable.
Something about generate previews…
Hello @ratsoundsystems,
Thank you for updating the uploader, and I’m sorry to hear that the error still persists 
To assist you further, could you please provide us with the settings of the element that is returning the error? We have attempted to recreate the issue on our end but have not been successful thus far. Your input will be invaluable for our developers to investigate the problem more effectively.
Thank you for your patience, and please accept our apologies for any inconvenience.
Have a fantastic Monday!