Please any one tell me how to upload file more than 500mb, because i am uploading file less than 500mb (like 470mb or 430mb). It's working fine but when upload 600mb 700mb file then show error.
My php.ini settings are:
upload_max_filesize=2048M
post_max_size=2048M
max_execution_time=3000 (50 minutes)
memory_limit=1024M
File read is 100% but when goes to write then shows error.I don't know where is the problem.
Related
I am trying to upload a file larger than 40MB but it fails and i get below error:
<Error> <Code>EntityTooLarge</Code> <Message>Your proposed upload exceeds the maximum allowed size</Message> <ProposedSize>41945391</ProposedSize> <MaxSizeAllowed>41943040</MaxSizeAllowed> <RequestId>yyy</RequestId> <HostId>xxx</HostId> </Error>
Contacted Amazon and they have confirmed that they haven't put any restriction on our bucket.
I am using ng-file-upload directive to upload the file. Did anyone had this problem using ng-file-upload angular directive while uploading file larger than 40MB.
I have checked .js files in above directive and cant see anything checking the size but want to double check if i am missing something.
Thanks in advance.
The problem was in the policy signature we were creating and in it, we were giving the max_size as 40MB
I am trying to upload files that are larger than 100 MB through Cloudflare's network.
I want everything to run through Cloudflare's network because I don't want my website's IP to be known to the world.
Plupload can be used to chunk files before uploading them to the server.
This is what it says on Plupload's home page.
Upload in Chunks
Files that have to be uploaded can be small or huge - about several
gigabytes in size. In such cases standard upload may fail, since
browsers still cannot handle it properly. We slice the files in chunks
and send them out one by one. You can then safely collect them on the
server and combine into original file.
As a bonus this way you can overcome a server's constraints on
uploaded file sizes, if any.
The last part is what catches my eyes.
So can I use Plupload to bypass the 100 MB limit set by Cloudflare?
I've tested this out and you can pass CloudFlare's limit by using plupload's chunking. CloudFlare limits a single file upload that is over 100MB so if we chunk it to say 90MB we would be sending 90MB file through CloudFlare's and that's not an issue.
Yes, chunking your uploads can work, I used ResumableJS to get around the upload limit.
I use Responsive Filemanager for several websites that I host. I have the latest version (9.6.6) installed, and I also use the tinyMCE plugin for the Jquery tinyMCE version 4, but my problem occurs with both the standalone filemanager as well as the plugin, so I doubt this is important.
Anyhow, my problem is the following: everything seems to be working just fine when I upload files smaller than exactly 2 megabytes. Using a dummy file generator, I have been able to generate a PFD file of exactly 2097152 bytes, which uploads fine, and a PDF file of 2097153 bytes, which doesn't upload.
Responsive Filemanager always says the upload went fine (with both the Standard Uploader and the JAVA uploader), but any file bigger than 2097152 bytes doesn't actually get uploaded.
Here's a video demonstrating precicely what the problem is: https://youtu.be/NDtZHS6FYvg
Since my RF config allows files up to 100MB (see entire config here: http://pastebin.com/H9fvh1Pg), I'm guessing it might be something with my server settings? I'm using XAMPP for Windows. Could it be that there are some settings in my Apache config or something like that, which block uploads through http bigger than 2MB?
Thank you for your help!
EDIT: typo's and added links + video showing the problem.
I managed to find the solution for my own problem. I couldn't believe some sort of bug would cause any file exactly bigger than 2 MB to fail, so after a while I finally figured out it had to be something with the server itself, and indeed, in the php.ini I found the following line:
upload_max_filesize = 2M
Changing this to a bigger number fixed the problem for me. Would be nice if ResponsiveFileManager had a way of informing the user about the fact that the upload did in fact not complete successfully due to a php.ini server setting, but ah well...
You just need to change the config file of responsivefilemanager, i.e config.php
'MaxSizeUpload' => 10,
Just change the MaxSizeUpload variable and check.
I am uploading files by servlet/JSP. Now I am facing an issue about getting the created time of the uploaded file.
The problem is, when a file is uploaded to server, I get the created time and find it same as uploaded time. The file is created on server when uploading finishes...
Is it possible to get the original created time of an uploaded file?
Not directly, but you can ty this workaround. When you upload the file, get the creation time and update a README.txt file on the server. This README.txt will have entries like this:
UploadedFileName: Creation Time of Upload File
I have an issue where occasionally I need to work at Starbucks.
When I upload a PHP file the connection is slow so if a user tries to access the PHP file while I am uploading it they will of course be issues a fatal error.
This is very inconvenient to my busy websites. Is there a way that when a file is uploaded it can be uploaded to a temporary location, and then the server moves it to the real location once finished?
You can make WinSCP upload the file to temporary file and rename it once transfer completes automatically.
In Preferences go to the Transfer > Endurance tab and select All Files in the Enable ... Transfer to temporary file name box.
For details refer to:
https://winscp.net/eng/docs/ui_pref_resume
Why don't you just upload the file to a temporary folder on the server and execute commands on the server to remove the old file and move the new file? It should move the file fast enough on the server to eliminate any hiccups the users would see unless their timing was just right.