Forum Replies Created
On HTTP I can get the 2GB links to download *most* of the time
On HTTPS they almost always fail.
They always die right towards the end.
When I click on “resume” in Chrome, it resumes and completes.
Having spent all day long fighting with this and trying to figure out the problem, I finally have half of the answer: the hosting site (WPengine) has a script that runs, killing any process that lasts more than 1 minute. So that is why small files are fine and large ones stall.
I have figured out a way around this (for now) by dropping the files in a different (non-WPDM) folder and using a URL. It is slow, but it works.
However, this leads me to the next question: If I am able to convince the customer to use either dropbox or google drive, will I have a similar issue?
Using Safari on the original system with an older 2GB ISO file dies at 125.8MB with a message of “cannot parse response”
Tried this on my domain. With 500MB file it works. 2GB file crapped out after ~1.5GB on the first try. Trying it a second time.
OK, figured out that is requires “edit_page” access to be able to download. In my mind this is a big security issue.
I have updated all of the user roles and the roles are able to download now. I had to install a dashboard restriction plugin so that they cannot get into the dashboard.
Also, just to test because the upload is behind a password protected page I tried to create a test page, getting the same problem.
Feels like a path setting.