Templates Plugins Courses

AWS file uploader plugin timing out

Hi there, I just installed the AWS Uploader plugin for Bubble. I set it up so I can upload small images, but when I try to upload videos off 400mb+ I invariably get a timeout error. I’ve set up the timeout value up to 600 seconds without success. Is there any other setting to tweak?

thanks.

Hi @tariuk,

Thanks for reaching out. Unfortunately, this issue is not reproducing on our side. Could you please provide the following details:

  1. screenshots and/or screencast of your app setups (group, reusable element etc. where plugin element is placed)
  2. plugin element settings (all fields and checkboxes to be visible)
  3. browser and OS version you are using to develop the app
  4. share the files you are trying to upload
  5. error messages and console logs

So we can have a much better investigation to see whether or not it is plugin related, then come back with working solutions asap.

Best,
Alex

I don’t think that there are any complexities to how I set it up. The uploader is inside a group in the main page (no reusable elements). Here are screenshots of the set up. The file is any large file. I’m using Firefox on a Mac.

I have succeeded with the upload if I set up the timeout time to something like 10000 seconds. Am I right to understand then that this timeout is the time needed to complete the whole upload, and not just a means to keep the connection alive? If so, then clearly this should be a pretty large number if we expect to upload files that are a in the GBs.

I also have a different question: The FileUploadNoGUI element adds a random string prefix to my files, and doesn’t expose the original filename as far as I can tell. Furthermore, this random string is of variable length (sometimes “zq_” plus 10 characters, sometimes 11) which makes it hard to remove it. Is there a way to preserve the original filename so that I can present it to the user? If there’s a way to accomplish something similar with actions on a GUI uploader I would also be interested.

Hi @tariuk,

Thanks for feedback. Yes, the timing needs to be set up so it actually keeps the connection alive so library which plugin is based on can actually upload the large file. In this case it really depends on multiple variables besides plugin element settings, like device you are running this app on, Internet connection, speed, Bubble plan etc.

So in case it is a super fast device, you will not even see how it loads the file. Uploading large files is also dependent on Bubble plan of your app, because Bubble Hobby for example doesn’t let you upload more than 2GB, as this is the maximum file storage. And it also limits you to 5GB per upload. You can find more information here and here.

Unfortunately, there isn’t a way to remove the prefix through plugin for NoGUI uploader, because it is set on purpose to differentiate the unique files to be uploaded to your S3 bucket, because AWS overrides the uploaded files with same name. Even with GUI uploader, we are still adding a unique ID to whether filename, or folder name and then insert the file into created folder:

image

It still creates a random String of characters so AWS differentiates the uploaded files.

We’ll take your feedback for future improvements if feasible. :pray:

Hope it helps.

Hi Alexandru,

Thanks for your reply. I have several questions in response.

Yes, the timing needs to be set up so it actually keeps the connection alive so library which plugin is based on can actually upload the large file

Do I understand correctly then that this number needs to be a really really high number to accommodate for all possible file sizes, devices and internet connections that my users may have? Is there a limit to how big I can make this timeout value?

Uploading large files is also dependent on Bubble plan of your app, because Bubble Hobby for example doesn’t let you upload more than 2GB, as this is the maximum file storage. And it also limits you to 5GB per upload

I’m uploading things to my own S3 bucket, not Bubble’s, so I’m not sure how this relates. The name of the plugin is “AWS File Uploader No File Size Limits”, so how is Bubble storage limit relevant?

Unfortunately, there isn’t a way to remove the prefix through plugin for NoGUI uploader, because it is set on purpose to differentiate the unique files to be uploaded to your S3 bucket, because AWS overrides the uploaded files with same name

Is there a way to make the random string consistent, having a fixed number of characters, or including a separator, or any other means to be able to remove it with regular expressions for showing to the user?

Even with GUI uploader, we are still adding a unique ID to whether filename, or folder name and then insert the file into created folder

The difference is that if I use the GUI Uploader, when I refer to the Uploader’s filename, I get the filename, not the uuid_filename. With the NoGUI Uploader, the filename is zq_randomstringfilename. Is there a way to use a hidden GUI Uploader triggered with a workflow or something of that sort?

Hi @tariuk,

Thanks for feedback. Let me provide more insights here.

Unfortunately, there isn’t mentioned a limit number for max timeout, but you can try something like this:

image

To test things out, and it is going to work properly. But yes, if you want your users to upload large files so that device power and internet connection etc. do not cause any troubles - it needs to be a large value.

The thing is that you are running this plugin through Bubble engine, which has its own limitations. In this case, the maximum size per upload is limited to 5GB. This information can be found here. Also, there is a limitation at browser level that can cause trouble, as well as your Bubble engine version - because only apps on Version 6 or higher have this functionality of 5GB per upload… Versions 5 and below are still capped at the 50 MB limit. You can check out the forum announcement for this feature here: https://forum.bubble.io/t/new-feature-beta-large-file-uploads/84395.

Unfortunately, there isn’t a way to influence on this prefix with plugin per se, but you can try to use a regex as possible workaround.

I’m afraid it is not possible at the moment, but we’ll consider it as improvement for future updates :pray:

Hope it helps

To be honest, no, it doesn’t help much at all. You charge money for this plugin and I expect a little more effort to address these issues.

The thing is that you are running this plugin through Bubble engine, which has its own limitations

So "AWS File Uploader No File Size Limits” has the same size limits as Bubble’s native uploader? How is that not an extremely disingenuous name? Why is this not mentioned on the plugin’s page? Instead the first thing you say is that it “allows you or your users to upload files from Bubble apps directly to your AWS (Amazon Web Services) without any file size limits.

Unfortunately, there isn’t a way to influence on this prefix with plugin per se, but you can try to use a regex as possible workaround.

There is. I think an inconsistent uuid scheme and no separator is clearly just something that needs to be fixed, so what you do is you fix it push an update. That’s what you do when you take responsibility for the products you sell, and it takes less time than it took you to write that reply. You tell me how do I use regex to extract a random string of variable length that has no separator.

Hello @tariuk

Thanks for feedback and sorry for your experience with our plugin. :pray:

However let me jump in here and provide some information on the matter.

Plugin indeed does not has any file size limits as the description suggests. The plugin offers possibility to limit the upload size by setting the right proprieties.
What Alex mentioned is that there are limitations by both bubble and browsers alike - https://www.smartfile.com/blog/file-size-limits-for-uploads-through-web-browsers/
https://forum.bubble.io/t/new-feature-beta-large-file-uploads/84395
so even with that, the plugin does not has any limits set.
That is why the plugin works as intended.

Regarding the random string that is not what is "desired’ for your specific use case, we can not provide at the moment a “fix” since there is nothing to fix. Over 95% of respondents did not find this as a “bug” per se so at the moment we can not jump and modify the structure of our algorithm , I’m afraid.

However we’ve taken into consideration everything provided to check if and how feasible is it to implement.

For regex option you can try and find out more on main bubble forum how to use it - https://forum.bubble.io/search?q=regex%20help
Also check https://regex101.com/

Thanks for understanding. :pray:
Hope this helps.

Regards,
Dumitru

Hello Dumitru,

Regarding the random string that is not what is "desired’ for your specific use case, we can not provide at the moment a “fix” since there is nothing to fix. Over 95% of respondents did not find this as a “bug” per se

I’m not sure what 95% of people you asked about this and told you this is not a bug, but I think anybody (and I believe you too) would agree that this is at a minimum inconsistent behavior (GUI uploader’s filename returns the filename, NoGUI uploader’s filename returns randomstringfilename; GUI uploader has uuid of consistent length, NoGUI uploader has uuid of variable length). And it makes it impossible to do something that is a very reasonable expectation to have: to return the name of the file that was uploaded. So you may say that it’s not a bug and that it’s my ‘desires’ that are not being met, but I honestly believe that given how simple it is to fix this, any programmer with integrity would want to address these issues regardless of the percentage of users for which this is a problem. I know I would.

so at the moment we can not jump and modify the structure of our algorithm , I’m afraid.

Adding an underscore at the end of the uuid or checking that the length is always the same is not “modifying the structure of your algorithm”. And it takes significantly less time than it took you and Alexandru and me to write these messages.

However we’ve taken into consideration everything provided to check if and how feasible is it to implement.

Thank you. Please let me know when you have an estimate on when this could be addressed.

For regex option you can try and find out more on main bubble forum how to use it - https://forum.bubble.io/search?q=regex%20help
Also check https://regex101.com/

I know how to use regular expressions, thank you, that’s how I know that you can’t remove something that you don’t know how long it is, has all kinds of characters and has no separator.

Thanks for understanding. :pray:

I do try to understand you, and I hope that you try to understand me too. I want to be able to use this plugin to address a pressing need that I have, and I want to feel thankful that you guys made it and to give it a great review and maybe even feel like I had a tiny contribution towards making it just a little bit more useful for other people as well. I would imagine that you’d want the same things.

Hi @tariuk

Thank you for your feedback. :pray:

We’ll take a look at it and we’ll see how and what is feasible to be implemented. We’ll notify as soon as possible about it.

Regards,
Dumitru

Any news on this? I’m still needing it

Hello @tariuk

Thanks for checking back with us :pray:

Currently we’re working on the update, once it’ll be available we’ll notify you.
Thanks for understanding.

Regards,
Dumitru

Hello @tariuk

Thanks for patience and feedback.

We’ve pushed the update to live, please upgrade the plugin, place new element on page, provide the settings and give it a try. :pray:

Also please do check out the docs - https://docs.zeroqode.com/plugins/aws-file-uploader-plugin#file-upload-no-gui-element
for more details.

Regards,
Dumitru