cannot upload big size file ( 20M) due to timeout

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • zatou
    Junior Member
    • Mar 2018
    • 12

    cannot upload big size file ( 20M) due to timeout

    I can not upload a file that is +10 MB because of a timeout.
    avoiding modify php.ini, i have a espo.ini in /etc/php/../apache2/conf.d where I modify the values:
    max_execution_time 180
    max_input_time 180
    post_max_size 50M
    upload_max_filesize 50M
    But after 60 seconds I get a timeout. Is the problem not located on the client side?
  • yuri
    Member
    • Mar 2014
    • 8440

    #2
    Seems you are right. There must be a 60 seconds timeout for ajax requests. I will check and fix.
    If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

    Comment

    • zatou
      Junior Member
      • Mar 2018
      • 12

      #3
      Thanks yuri keep me informed please.

      Comment

      • yuri
        Member
        • Mar 2014
        • 8440

        #4
        Fix: https://github.com/espocrm/espocrm/c...578bb1cf7565bc
        If you find EspoCRM good, we would greatly appreciate if you could give the project a star on GitHub. We believe our work truly deserves more recognition. Thanks.

        Comment

        • zatou
          Junior Member
          • Mar 2018
          • 12

          #5
          Thanx

          Comment

          • caohee
            Junior Member
            • Aug 2018
            • 4

            #6

            Friends, I need some help. Does this method work with the current version of espocrm? If yes, what is the current name of the files? I can not find file.js in the current version. Thank you very much in advance. (Sorry bad english)

            Comment

            • tanya
              Senior Member
              • Jun 2014
              • 4308

              #7
              Hello,
              do you get timeout error while uploading files?
              Yes, this fix exists in current version

              Comment

              Working...