Search Engine: Elastic

Article ID: 126985, created on Sep 23, 2015, last review on Sep 17, 2016

  • Applies to:
  • Operations Automation 6.0
  • Operations Automation 5.5


When customer accesses File Manager in CP, he receives an error:

Unable to connect to backend.

The error occurs for a single webspace that hosts a large amount of files. Other subscriptions are not affected.


It takes a huge amount of time to scan through the webspace files, and the default web server or PHP timeouts are not enough to serve the request.


Increase the possible timeouts:

  1. Linux File Manager.

    • Apache web server:

      • Edit timeout value in /etc/httpd/conf/httpd.conf
      • Reload Apache configuration:

        # service httpd reload
    • PHP:

      • Edit max_execution_time in /usr/local/pem/sysvhosts/elFinder/conf/php.ini
      • Reload Apache configuration:

        # service httpd reload

    Note, in case File Manager is deployed on an NG cluster, the above settings should be configured on all servers in the cluster.

  2. Windows File Manager.

    • IIS web server:

      • Open Internet Information Services (IIS) Manager and expand Sites list.
      • Select File Manager Web Site and click Advanced Settings in the Actions pane.
      • Expand Behaviour tab and set the desired value for "Connection Timeout" field.
    • PHP:

      • Edit max_execution_time in C:\Program Files (x86)\SWsoft\PEM\sysvhosts\elFinder\conf\php.ini and ensure that the activityTimeout does not override it - check official IIS documentation for details.

        Command to add/increase activityTimeout:

        %windir%\system32\inetsrv\appcmd set config -section:system.webServer/fastCgi /[fullPath='C:\php\php-cgi.exe'].activityTimeout:600

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 956c448bddc7e1f3585373687602379f 6f1456866eed87488c0f02b298a741c0 5b048d9bddf8048a00aba7e0bdadef37 2554725ed606193dd9bbce21365bed4e

Email subscription for changes to this article
Save as PDF