How to Change Maximum Upload File Size in Owncloud

Uploading big files > 512MB¶

The default maximum file size for uploads, in ownCloud, is 512MB. Yous tin increase this limit up to the maximum file size which your filesystem, operating organization, or other software allows, for example:

• < 2GB on a 32Bit OS-architecture
• < 2GB with IE6 - IE8
• < 4GB with IE9 - IE11

64-flake filesystems have much college limits. Please consult the documentation for your filesystem.

Note

The ownCloud sync client itself however is able to upload files of whatsoever size, every bit it uploads files by transmitting them in small chunks. But, it tin can never exceed the maximum file size limits of the remote host.

System Configuration¶

• Make sure that the latest version of PHP (at to the lowest degree 5.half dozen) is installed
• Disable user quotas, which makes them unlimited
• Your temp file or partition has to exist big enough to agree multiple parallel uploads from multiple users; due east.yard. if the max upload size is 10GB and the average number of users uploading at the same time is 100: temp space has to hold at least 10x100 GB

Configuring Your Web server¶

Annotation

ownCloud comes with its own owncloud/.htaccess file. Because php-fpm can't read PHP settings in .htaccess these settings must be set up in the owncloud/.user.ini file.

Set the following two parameters inside the corresponding php.ini file (see the Loaded Configuration File section of PHP Version and Information to find your relevant php.ini files)

                            php_value              upload_max_filesize              =              16              G              php_value              post_max_size              =              16              Thou            

Arrange these values for your needs. If you lot encounter PHP timeouts in your logfiles, increase the timeout values, which are in seconds:

                            php_value              max_input_time              3600              php_value              max_execution_time              3600            

The mod_reqtimeout Apache module could also end big uploads from completing. If yous're using this module and getting failed uploads of large files either disable it in your Apache config or enhance the configured RequestReadTimeout timeouts.

There are also several other configuration options in your Web server config which could prevent the upload of larger files. Please see the manual of your Web server for how to configure those values correctly:

Apache with mod_fcgid¶

• FcgidMaxRequestInMem
• FcgidMaxRequestLen

Note

If you are using Apache/2.4 with mod_fcgid, every bit of February/March 2016, FcgidMaxRequestInMem however needs to exist significantly increased from its default value to avoid the occurence of segmentation faults when uploading big files. This is not a regular setting just serves as a workaround for Apache with mod_fcgid problems #51747.

Setting FcgidMaxRequestInMem significantly higher than normal may no longer be necessary, once bug #51747 is fixed.

NGINX¶

• client_max_body_size
• fastcgi_read_timeout
• client_body_temp_path

Since NGINX i.7.xi a new config option fastcgi_request_buffering is availabe. Setting this selection to fastcgi_request_buffering off; in your NGINX config might help with timeouts during the upload. Furthermore it helps if you're running out of disc space on the /tmp segmentation of your arrangement.

For more info how to configure NGINX to raise the upload limits encounter also this wiki entry.

Note

Make sure that client_body_temp_path points to a partitioning with adequate space for your upload file size, and on the aforementioned partition every bit the upload_tmp_dir or tempdirectory (come across below). For optimal performance, place these on a carve up hard drive that is dedicated to bandy and temp storage.

If your site is backside a NGINX frontend (for case a loadbalancer):

By default, downloads will exist express to 1GB due to proxy_buffering and proxy_max_temp_file_size on the frontend.

• If yous tin can access the frontend's configuration, disable proxy_buffering or increase proxy_max_temp_file_size from the default 1GB.
• If you do not take admission to the frontend, set the X-Accel-Buffering header to add_header X-Accel-Buffering no; on your backend server.

Configuring PHP¶

If you don't want to use the ownCloud .htaccess or .user.ini file, y'all may configure PHP instead. Brand certain to comment out whatever lines .htaccess pertaining to upload size, if you entered any.

If you are running ownCloud on a 32-bit arrangement, any open_basedir directive in your php.ini file needs to be commented out.

Set the following 2 parameters within php.ini , using your own desired file size values:

                            upload_max_filesize              =              sixteen              G              post_max_size              =              16              G            

Tell PHP which temp file you want it to use:

                            upload_tmp_dir              =              /              var              /              big_temp_file              /            

Output Buffering must be turned off in .htaccess or .user.ini or php.ini , or PHP will return memory-related errors:

• output_buffering = 0

Configuring ownCloud¶

As an alternative to the upload_tmp_dir of PHP (e.yard., if you don't have access to your php.ini ) you can also configure a temporary location for uploaded files by using the tempdirectory setting in your config.php (Come across Config.php Parameters).

If you have configured the session_lifetime setting in your config.php (See Config.php Parameters) file then make sure it is not too depression. This setting needs to be configured to at least the time (in seconds) that the longest upload volition accept. If unsure remove this completely from your configuration to reset it to the default shown in the config.sample.php .

Configuring upload limits inside the GUI¶

If all prerequisites described in this documentation are in place an admin tin alter the upload limits on demand by using the File handling input box within the authoritative backend of ownCloud.

Depending on your environment y'all might get an bereft permissions message shown for this input box.

To be able to use this input box y'all need to make sure that:

• Your Web server is be able to employ the .htaccess file shipped by ownCloud (Apache merely)
• The user your Web server is running as has write permissions to the files .htaccess and .user.ini

Set Strong Directory Permissions might prevent write access to these files. Every bit an admin you demand to make up one's mind between the ability to use the input box and a more secure ownCloud installation where you need to manually modify the upload limits in the .htaccess and .user.ini files described in a higher place.

Full general upload issues¶

Diverse environmental factors could cause a brake of the upload size. Examples are:

• The LVE Manager of CloudLinux which sets a I/O limit
• Some services like Cloudflare are also known to cause uploading bug
• Upload limits enforced past proxies used past your clients
• Other webserver modules like described in General Troubleshooting

walkerthopilt.blogspot.com

Source: https://memoriaferroviaria.rosana.unesp.br/pmf2/owncloud/core/doc/admin/configuration/files/big_file_upload_configuration.html

Share this post