Error connexion when trying to upload a "big" file

Error connexion when trying to upload a "big" file

by Guillaume Antier -
Number of replies: 6
Hello,

When I try to upload a big file (100mo) the upload begins but, before the end, I get an error (cf. attached screenshot).

I think Apache and PHP are already well configured :
Apache
LimitRequestBody 157286400
PHP
post_max_size = 150M
upload_max_filesize = 150M

Do you have any idea to help me ?
Regards.
Attachment error.gif
Average of ratings: -
In reply to Guillaume Antier

Re: Error connexion when trying to upload a "big" file

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers
Is this a multiple server set up?  Could there be an issue between the multiple servers?
In reply to Emma Richardson

Re: Error connexion when trying to upload a "big" file

by Guillaume Antier -
No, it is a "standalone" simple server.
In reply to Guillaume Antier

Re: Error connexion when trying to upload a "big" file

by Guillaume Antier -
As I have an ssh access to the server, is it possible to upload the file somewhere in the moodedata directory and the selet it through the file selector ?
In reply to Guillaume Antier

Re: Error connexion when trying to upload a "big" file

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers

You should be able to set up a local folder as a repository in Moodle and then you could achieve this.

In reply to Emma Richardson

Re: Error connexion when trying to upload a "big" file

by Guillaume Antier -
I succeded this way. It is ok for now but it is still strange.
And I have to upload the file myself whereas I think that users could do it by themself :/
In reply to Guillaume Antier

Re: Error connexion when trying to upload a "big" file

by Emma Richardson -
Picture of Documentation writers Picture of Particularly helpful Moodlers Picture of Plugin developers

They should but I suspect you are hitting a timeout somewhere.  Try upping the max_execution_timeout.