And now I get this error:
Public use of objects is not allowed by this account. Please contact Wasabi Support at support@wasabi.com for assistance.
And now I get this error in debug mode:
The image could not be loaded: https://s3.eu-west-1.wasabisys.com/bs-survey/dashinmaz-emlak/depositphotos_36220949-stock-photo-beautiful-landscape.jpg .
17:42:25
General warning
The image could not be loaded: https://s3.eu-west-1.wasabisys.com/bs-survey/dashinmaz-emlak/Ekr.png .
17:42:25
General warning
The image could not be loaded: https://s3.eu-west-1.wasabisys.com/bs-survey/dashinmaz-emlak/Ekr.png .
Hi @v.aliquliyev,
Regarding your first message, I understand that the error with “generate_preview” is still present in the latest update.
As for the second error you mentioned, it’s important to note that Wasabi no longer allows users to change their bucket settings to be public for everyone. Therefore, the error you’re experiencing is likely due to the settings of your Wasabi S3Bucket, and it doesn’t originate from our end. This is likely the reason for the general warning about images not being able to load on your page.
As a suggestion, please review your bucket policy and ensure that you grant permissions for your application to read the files. This way, you should be able to display images from Wasabi on your app while restricting access to other users.
Wishing you a great day ahead 
please, could you tell me how to do this?
Hello @v.aliquliyev,
Could you please confirm whether the “generate_preview” error is still occurring? If it persists, we would appreciate it if you could grant us collaboration rights to your project so that we can investigate the issue further. Please provide us with a step-by-step description of where the element is located on the page, any necessary credentials, and any other details that would help us understand the root cause of this problem.
To grant collaboration rights, navigate to the settings in the plugin editor, click on “Collaborators,” and add our email address, support@zeroqode.com, to the list. You may encounter a red error message, but please ignore it, as we are on an agency plan.
Regarding the Bucket Policy, here is an example of how we have configured our buckets:
{
"Id": "acceptsonlyhttpreferer",
"Version": "2012-10-17",
"Statement": [
{
"Sid": "Public",
"Effect": "Deny",
"Principal": {
"AWS": "*"
},
"Action": "s3:GetObject",
"Resource": "arn:aws:s3:::BUCKET-NAME/*",
"Condition": {
"StringNotLike": {
"aws:Referer": [
"URL OF THE PAGES WHERE THE IMAGES ARE/*",
"URL OF THE PAGES WHERE THE IMAGES ARE/*",
"URL OF THE PAGES WHERE THE IMAGES ARE/*"
]
}
}
}
]
}
Please modify the code according to your specific bucket and domain settings.
Wishing you a great day
Unfortunately this didn’t help me either 
I can’t even imagine why. I wrote out the policy with the accuracy that you defined (with changes to the domain and cart), I opened the editor of your demo page and did everything one to one, but on your demo page the files that were taken from Wasabi are shown, but they are not shown on mine.
Hi @v.aliquliyev,
I apologize for the misinformation earlier. I’ve had a conversation with the developer regarding the recent changes made by Wasabi.
Currently, there is no option to make a bucket public, even with the use of policies. If you want to make your bucket accessible to specific domains like your application, you’ll need to reach out to Wasabi’s support team and request them to make the bucket public. Once they’ve made it public, you can then add the policy as mentioned earlier to allow access to file information on your domains.
I’m sorry for any confusion, and I appreciate your understanding 
Wishing you a wonderful Thanksgiving! 
1 Like
I’ve been a long user of this plugin. I didn’t update the plugin versions since it worked well for us anyway. We’ve been using the version “1.74.0 - Removed Parameters field from file states” ever since.
However, with the new bubble plugin requirement where old plugins would need to migrate to version 4 of the plugins editor, we had to update to the version “1.95.0”
But when we updated, the plugin suddenly doesn’t work. We can’t upload files.
I haven’t been able to check the recent updates of the plugin so I’m not sure if there are new requirements to make it work. As far as I’ve checked, the updates have been only fixes, no big updates that would require us to do something. That said, we shouldn’t be experiencing any issues, right?
Would mean so much to us if you could help us find the issue or any new actions / things we need to do to keep up with the new updates.
Hi @ntabs,
Thank you for reaching out to us!
If you have already updated the plugin, we recommend updating it to the latest version as well. In the latest version, there have been some changes to the way you configure the plugin. Now, you will need to input the secret and access keys inside the Wasabi element. Unfortunately, I cannot provide you with all the details of the changes that have been made up to this point.
To ensure that everything is set up correctly, please double-check the settings and review any issues detected by Bubble, as addressing these issues may be essential to getting the functionality to work properly.
If you have any questions or need further assistance, please don’t hesitate to reach out to us
Wishing you a great day ahead
Hello,
I recently purchased your plugin for uploading images and videos to Wasabi and need some assistance due to unclear aspects in the documentation.
- Uploading Issue: I am using a camera plugin to capture photos with the device’s native camera. After taking a photo, I save it in a custom state as an image. However, when I attempt to upload it to Wasabi using the “Upload Base64 WasabiS3 A” workflow, I encounter an error stating “No file upload.” Could you please guide me on what I might be doing incorrectly?
- Displaying Images in My App: Once images are uploaded to Wasabi, I’d like to display them in my app. What is the recommended method for saving these images in my database? Should I save them as image files or as URLs?
- Image Accessibility: Is it possible to display the images stored in Wasabi directly in my app?
Your guidance on these matters would be greatly appreciated.
Thank you.
Hi @condocrm
Thank you for your message and purchase, sorry for the delayed reply over the weekend
Regarding your questions:
For the Uploading Issue please try the following:
- Verify that your workflow is correctly set up to pass the Base64 string to the Wasabi upload action. The data should be correctly referenced from the custom state where you’ve saved the image.
- Double-check the camera plugin settings to ensure it’s configured to output the image in a format compatible with the Wasabi upload action.
As for Displaying Images:
The recommended approach is “Save as URLs”. After uploading an image to Wasabi, you receive a URL to the stored file. Save this URL in your app’s database.
About Image Accessibility:
Yes, it is possible to display images stored in Wasabi directly in your Bubble app. After uploading images to Wasabi, store the URLs of these images in your app’s database. Then you can use those URLs to set them as sources for different elements.
In case you have other plugin-related questions please let me know.
Regards,
Hello @ZeroqodeSupport !
A quick question - I’ve deployed this plugin successfully across my app and haven’t had an issue, until I tried to run it on mobile.
I’m using the Wasabi element on my pages. For mobile users, it pops up an option to access the Photo Library, Take a Photo or Choose File. I’m able to load an image and preview it in the loader just fine. When I initiate the workflow to upload the image, it doesn’t. It creates all other actions in the workflow, but fails to upload the image.
Any idea?
Andy
Hello @andy4,
Thank you so much for reaching out.
We are currently looking into your inquiry and will respond to you as soon as possible.
We appreciate your patience and cooperation 
Cheers 
Hello @andy4,
We’re sorry for the delay in responding to your query
After conducting tests on our demo page using an iPhone with the Firefox browser, we didn’t experience any issues. The files were successfully uploaded to the Wasabi Bucket.
To delve deeper into your situation, could you please provide screenshots detailing how you’ve configured the plugin element and the workflows? It would also be helpful if you could specify the browser, model and operating system of the device where you’ve encountered this problem. This information will assist us in investigating and addressing the issue.
We look forward to your response and are here to assist you further.
Best regards,
Hello @ZeroqodeSupport
After updating to the latest version of the plugin (1.104.0) in case the element is invisible:
the plugin reports the following error:
Missing credentials in config
in case of any reference in the workflow (for example: Action Delete Files/Folders WasabiS3). Of course, the relevant access codes were entered by me in the element.
Hello @zukowski.kuba ,
Thanks for reaching out and for using our plugin.
We are sorry to learn about the difficulties you’re facing with the plugin. After doing some tests, we didn’t manage to reproduce the same error you are getting.
To understand better your use case, would it be possible to share more details about your setup? Namely, screenshots and screencasts of your workflow setup, plugin element, and the issue you see, for screencast recording we can suggest using the Loom tool.
Also, it would be extremely useful if you could create a video in step-by-step mode with the browser’s console enabled, from where you open the page to the moment when you see the error.
This information will greatly assist us in identifying and resolving any underlying factors.
Thank you once again for your cooperation and patience. We are looking forward to your response.
Best regards,
Zeroqode Support team
More information below:
- I have your element in the following configuration (Group Focus). Wasabi is never visible. It is hidden but I use it in the workflow.
Element data:
- The workflow looks as follows:
- When I run a particular workflow on the site I immediately get information in the console:
I have not changed my approach at workflow over the last few months. I have only upgraded the version of your plugin (well, and of course entered the appropriate codes for the element). Interestingly as the wasabi element is visible => the workflow executes without error.
Hello @zukowski.kuba,
Thank you for providing additional details regarding your query.
Upon consultation with our team, we have confirmed that the Wasabi s3 element does indeed need to be visible on the page. Following an update aimed at enhancing security measures, it is now mandatory to insert the keys directly into the element, in addition to the plugin. This change was implemented to prevent unauthorized access to your secret keys via the application URL.
As a result, the element must be visible on the page to ensure the keys are also visible and the functionality operates as intended.
We appreciate your understanding and patience!
If you have any further questions or need assistance, please do not hesitate to reply.
Best regards,
Zeroqode Support Team
Hello,
A user reported to me today that he is unable to upload anything to my application.
I went to test and it is showing the error “Network Failure”.
I then went to the plugin page and the same error is appearing on the demo page.
Could you please check urgently?
Thanks!
2 Likes
Same here! Help @ZeroqodeSupport
plugin stopped working completely…
2 Likes