2.2.0-beta5: Presentation upload limit error

[Kenren Taisho]

Hi BBB devs,

Good afternoon.

I asked my users to use my 2.2.0-beta5 install and one user reported to me this morning that presentation uploading does not work as advertised (HTML5 client).
This is because I told them that the maximum file accepted is 100MB and the maximum number of page is 1000 pages.

• Here are the relevant configuration

/usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties

/etc/nginx/sites-available/bigbluebutton

• The user is just uploading a 36MB with 340 pages PDF file 

• However, we are having this error from BigBlueButton "File is too large, maximum of 200 pages reached"

Please tell me what configuration am I missing? I also cannot find the configuration about the 200 page limit.

More power and thanks in advance!

[Chad Pilkey]

There's a maximum file size restriction on the client-side also. https://github.com/bigbluebutton/bigbluebutton/blob/master/bigbluebutton-html5/private/config/settings.yml#L150-L151

I can't find any page number restriction on the client-side. I can't even find that string either to double check how it's used.

[Kenren Taisho]

Hi Chad,

Thank you for your reply, I appreciate it.

It seems it's a hardcoded message in https://github.com/bigbluebutton/bigbluebutton/blob/master/bigbluebutton-html5/private/locales/en.json

app.presentationUploder.upload.413": "File is too large, maximum of 200 pages reached,

 

There are other messages hardcoded with a 200-page limit as well:

"app.presentationUploder.conversion.pageCountExceeded": "Ops, the page count exceeded the limit of 200 pages",

Looking at https://github.com/bigbluebutton/bigbluebutton/blob/master/bigbluebutton-html5/imports/ui/components/presentation/presentation-uploader/component.jsx

413: {
    id: 'app.presentationUploder.upload.413',
    description: 'error that file exceed the size limit',
  }, 

The ID 413 pertains to the size limit of the file. So the error really is the file size and has nothing to do with the page count. 

While the

PAGE_COUNT_EXCEEDED: {
    id: 'app.presentationUploder.conversion.pageCountExceeded',
    description: 'warns the user that the conversion failed because of the page count',
  }, 

Is the warning for the page count but both have hardcoded 200 pages in the locale file.

More power and kind regards!

--
You received this message because you are subscribed to the Google Groups "BigBlueButton-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.
To post to this group, send email to bigblueb...@googlegroups.com.
Visit this group at https://groups.google.com/group/bigbluebutton-dev.
For more options, visit https://groups.google.com/d/optout.

[Chad Pilkey]

I completely missed the string in the en locale. I thought I searched for the text, but I guess I failed to type it in correctly. It looks like the upload error handler is taking the returned error code and trying to put a helpful message to the user. I think it's being used here, https://github.com/bigbluebutton/bigbluebutton/blob/master/bigbluebutton-html5/imports/ui/components/presentation/presentation-uploader/component.jsx#L456-L464. I'm not familiar with the file upload plugin that we're using so I don't know if the 413 is being returned from the code or from nginx. Does the upload go through once you've increased the size in settings.yml?

To unsubscribe from this group and stop receiving emails from it, send an email to bigblueb...@googlegroups.com.

[Kenren Taisho]

Hi Chad, 

Thanks for the heads up, the 413 code was indeed being returned from nginx:

019/04/23 10:07:42 [error] 18830#18830: *54 client intended to send too large body: 48246482 bytes, client: xx.xx.xx.xx, server: xx.xx.xx.xx, request: "POST /bigbluebutton/presentation/PresUploadToken-aykvfwylDEFAULT_PRESENTATION_POD-w_xhg8kvlpry8d/upload HTTP/1.1", host: "xx.xx.xx.xx", referrer: "https://xx.xx.xx.xx/html5client/join?sessionToken=pmzmpsfxhsrudgyq"

I should have looked into the nginx logs as well in the first place, my bad and I apologize for this. 

I followed the following documentation in increasing the size of the uploaded presentation: https://docs.bigbluebutton.org/install/install.html

Increase the file size for an uploaded presentation
The default maximum file upload size for an uploaded presentation is 30 MB.
To increase this size, edit /var/www/bigbluebutton/client/conf/config.xml and edit maxFileSize` to the new value (note: if you have the development environment you need to edit ~/dev/bigbluebutton/bigbluebutton-client/src/conf/config.xml and then rebuild the client).
Next, change the corresponding limit in nginx. Edit /etc/bigbluebutton/nginx/web.nginx and modify the value for client_max_body_size
       location /bigbluebutton {
           proxy_pass         http://127.0.0.1:8080;
           proxy_redirect     default;
           proxy_set_header   X-Forwarded-For $proxy_add_x_forwarded_for;
        # Allow 30M uploaded presentation document.
           client_max_body_size       30m;

Following the documentation, do the "/var/www/bigbluebutton/client/conf/config.xml" config file refers to the flash client only?

And can you confirm that the nginx location which (also) needs to have the correct client_max_body_size parameter is the 

location = /bigbluebutton/presentation/checkPresentation {
                        proxy_pass         http://127.0.0.1:8090;
                        ....
                        # Allow 30M uploaded presentation document.
                        client_max_body_size       100m;
                        client_body_buffer_size    128k;
                        .....

and not the location 

location /bigbluebutton {
...

 as mentioned above in the documentation?

I adjusted the  client_max_body_size parameter of the "/bigbluebutton/presentation/checkPresentation" and now I can upload the presentation successfully!

So to summarize: 

1. The "app.presentationUploder.upload.413": "File is too large, maximum of 200 pages reached" message refers to the file size being returned by nginx and not the number of pages.

2. The following are the configuration that needs to be changed to change the maximum size of the uploaded presentation:

• /usr/share/bbb-web/WEB-INF/classes/bigbluebutton.properties (html5)
  
• /usr/share/meteor/bundle/programs/server/assets/app/config/settings.yml (html5)
  
• /var/www/bigbluebutton/client/conf/config.xml (flash)
  
• /etc/bigbluebutton/nginx/web.nginx (/bigbluebutton/presentation/checkPresentation nginx location)

Is this correct?

More power and kind regards!

 

To unsubscribe from this group and stop receiving emails from it, send an email to bigbluebutton-...@googlegroups.com.

[Chad Pilkey]

The changes to bigbluebutton.properties and web.nginx are for the server-side checks and apply to both clients because the endpoint on the server is the same. The changes to settings.yml and config.xml are client-side checks and only apply to their respective clients.

For the editing of web.nginx, it does look like there are two locations that need to be changed and neither location was actually listed in the documentation.

I've updated the 2.2 documentation to match the new modifications, http://docs.bigbluebutton.org/2.2/customize.html#increase-the-file-size-for-an-uploaded-presentation. Thanks for the additional information and debugging.