im getting the same issue, “this image could not be loaded” in error log. Did you ever manage to find a fix?
No. We had to change the approach of getting files from Retrieving them to Presigned URLs.
Hi @anon68770203, thanks for your message.
To save a URL of a stored file, please retrieve files from storage first. In the case of your screenshot - you are saving files that are added to the S3 element but not uploaded yet to Wasabi.
Hi @cohereandnow, thanks for your question.
We’re afraid that upload speed can not be influenced by our plugin. Mainly it relates to the device, network, and bandwidth capacities, which we regretfully can not control.
In case a filetype is not recognized, please try to add the file’s MIME type instead. For .mpeg files it would be video/mpeg
See the reference here: MIME types (IANA media types) - HTTP | MDN
Hope these answers help. If there will be any other plugin-related questions, please let us know 
Regards,
Zeroqode Support Team
Hey @ZeroqodeSupport
Two questions here I can’t seem to find answers / fixes to, please:
- Uploading videos from a mobile iOS device, seem to auto compress videos, despite the compression setting on the uploader being set to no. Is there any other way to prevent this from happening?
- Is there a way to prevent the option to record video? This this is most likely an iOS thing, but wanted to check just in case.
Thanks
Hi @tyrelsmythe, thanks for your message.
Regretfully, both of the reported moments relate to the device used for upload (the plugin has no functionality included to compress a video file). In this case, our possibilities are limited, as we can not influence it from the plugin side.
But, see if methods from this link may help with the reported issue: Why does the iPhone automatically compress my video files? | Marvelous Help Center
Please let us know if there are any other plugin-related questions that we can help with.
Regards,
Zeroqode Support Team
I tried that and it’s still wasn’t allowing mpeg files.
I got the mpeg files working by using .mp4 even though the file type says mpeg-4.
I attached a link to screen recording. I noticed that when when one of the files are able to be added to the wasabi element, that the files that ARE compatible aren’t added to the wasabi element either. I have an example at the end of the video where I select 3 files that work and 1 one that doesn’t. You can see that none of the files that are compatible are added.
Is there way to allow the files that are compatible to be added to the wasabi element and simply exclude the ones that aren’t? WeTransfer - Send Large Files & Share Photos Online - Up to 2GB Free
Thanks for your help!
Hi @cohereandnow, thanks for your reply and shared video.
We will check this case internally to see what could be the solution. Once we get a result, we will let you know asap.
And about this question,
Please use the following screenshots for guidance.
- Select a data type from the app
- setup the API workflow
Hope this helps.
Regards,
Zeroqode Support Team
Hello again @ZeroqodeSupport, thanks for your previous answer it helps me a lot. I can’t fix an error, I can upload my images in folder for retreive it well but I can’t save the url in my bubble app.
Maybe its because I have a wasabi trial account and I didn’t pay for the moment ? When I tried to store it, it create it but didn’t store in my “link” field.
Thanks again
Hi @anon68770203, thanks for your message.
First, you need to separate the workflow that uploads the files from the workflow that retrieves the URLs.
- Upload files to Wasabi Screenshot by Lightshot
- Retrieve data about files Screenshot by Lightshot
- Use the event “File retrieved successfully” to save the URL Screenshot by Lightshot
Hope this helps. If there will be any other questions, please let me know.
Regards,
Zeroqode Support Team
We just started using Wasabi so I might be missing out on a couple of things.
When I was playing around, I can’t seem to access my files when I open it in my browser. It shows an error message saying “This XML file does not appear to have any style information associated with it. The document tree is shown below.”
I am well aware that this issue is caused by the file being private, However, I have already set it to public, not only the file but also its folder.
Attached below is a screenshot of the error
Here’s the file being set at as public yet it is still inaccessible when you view it in the URL.
Would greatly appreciate your help, thanks.
Hi, I found the solution.
It turns out they pushed an update recently about a change in ability to configure public access to objects and buckets.
More info about this update here: https://wasabi-support.zendesk.com/hc/en-us/articles/13615396482203-Change-in-Ability-to-configure-PUBLIC-Access-to-objects-and-buckets-?source=search
The solution would then be to use pre-signed URLs. More info here: https://wasabi-support.zendesk.com/hc/en-us/articles/360022853592-How-do-I-generate-pre-signed-URLs-for-temporary-access-with-Wasabi-?source=search
Yes, I’m having the same issue — as I also signed up after March 13th 2023
@ZeroqodeSupport do you have a solution for this?
Do we need to use pre-signed URLs, or is there another way of requesting and displaying e.g. an image saved on Wasabi?
Hello, we aren’t decide the riddle with test.pdf yet. So, we have to ask you one more time 
Question: Every time, when we upload list of images from Bubble storage to Wasabi through “Upload file to Wasabi from another cloud” command, inside every folder in Wasabi appears the file “test.pdf” and ours images.
We’ve changed default URL (link to test.pdf) to other, but "test.pdf " every time inside all new folders!
Here expressions settings:
What can be wrong with it?
We’ll be very appreciate if you help us!
Yeah most likely, you would need to use pre-signed URLs. Sucks for us too since it would prolong our process even more—we’re storing data that doesn’t need to be private.
However, this was stated in their announcement. "If, however, you have use cases that require public bucket access you may contact Wasabi support to request to enable the feature. "
We contacted Wasabi Support to enable us to set our buckets to public and they asked for a few details e.g. use case, company details, etc. We’re still waiting for their response. I’ll keep you updated!
Hi @ntabs and @cjrb, thanks for reporting this. We passed this to the developer team for research. Once they will share a feedback, we will let you know asap 
Thank you for understanding.
Hi @nerpa.custdev, thanks for your reply.
For a better understanding of your case, please add our Support Team email to the list of collaborators to your application and provide us a link to your application (as well as let us on which page and under which user we can replicate your case).
This will allow us to check your settings and run some tests to fix the mentioned problem.
To add our Support Team as a collaborator, you need to do the following steps in the Bubble Editor:
Settings > Collaboration > Add email support@zeroqode.com
Note: avoid the warning message regarding the plan, as we are an agency and you can easily add us to your collaborators.
Regards,
Zeroqode Support Team
Hi @ZeroqodeSupport!
We’ve sent the Email with links and other info to support@zeroqode.com and add them to Collaboration.
Looking forward to hear from you, thanks for your support!
@nerpa.custdev, your mail, and all shared details are well received.
We’ve passed them on to the developer team for research.
Once any feedback will appear, we will let you know asap.
Thank you for understanding.
Regards,
Zeroqode Support Team
Would it be possible for you to add a preview for videos? Currently, the plugin only has a preview for images. It would be awesome if you could add one for videos. At the moment, you would need to upload the videos first to your Wasabi bucket before you could even view them in a video player.
Having a state or trigger to know that a Wasabi S3 element has been changed (a file has been added) would be very helpful as well—similar to when an input's value is changed
The plugin docs also seems inaccurate https://docs.zeroqode.com/plugins/wasabi-cloud-storage
I was trying to do these specific actions—enabling my website to access the bucket during get requests
I tried to add this code snippet in my bucket’s policies
{ "Version": "2012-10-17", "Statement": [ { "Effect": "Allow", "Action": "s3:*", "Resource": "*", "Condition": { "StringLike": { "aws:Referer": "YOUR_WEB_SITE_FULL_URL" } } } ] }
Got an error while trying to implement the code above
Also tried
{ "Id": "acceptsonlyhttpreferer", "Version": "2012-10-17", "Statement": [ { "Sid": "Public", "Effect": "Deny", "Principal": { "AWS": "*" }, "Action": "s3:GetObject", "Resource": "arn:aws:s3:::YOUR_BUCKET_NAME_HERE/*", "Condition": { "StringNotLike": { "aws:Referer": [ "https://YOUR_BUBBLE_APP_URL_HERE/", "https://YOUR_BUBBLE_APP_URL_HERE/*", "https://console.wasabisys.com/", "https://console.wasabisys.com/*" ] } } } ] }
However, none of them worked. Tried retrieving files yet they still are unable to display in my app. This may be because Wasabi updated their policies regarding bucket privacy, not sure.
Please look further into this.
TL;DR: I’m trying to enable my app to view the objects in my bucket without needing pre-signed URLs
Hi @nerpa.custdev, let us share some news.
The developer team checked your case and shared the following feedback.
- Kindly note that folder structure is created by using
/, not, - Please be sure that in this field, the filename is passed with its extension (it should look like “название.png” or “name.jpg”, etc.
Please apply the advised changes and check in step-by-step mode if the values are passed properly. Let us know if there will be any additional plugin-related questions.
We’ve added these suggestions to the plan of plugin possible improvements. The developer team will check how feasible would be to add them in future updates.
Let us check this internally too. We will let you know once feedback will appear.
Thank you for understanding.
Regards,
Zeroqode Support Team