Search Engine: Elastic

Article ID: 132494, created on Apr 8, 2018, last review on Apr 8, 2018

  • Applies to:
  • Operations Automation 7.3


Linux File Manager is intermittently returning 503 errors:

Error 503
Sorry, the service is not available
Try to reload page later.

When refreshing the page, it is loaded properly.


There are 2 WebFileManager services running on different servers, so every time the File Manager is accessed, the WebFileManager service is chosen by round-robin algorithm from the available ones.

The corresponding rules can be found on the branding node:

[root@linuibr1 ~]# grep webfilemanager /var/www/brands/
RewriteRule ^webfilemanager/5043/(.*)$$1 [P]
RewriteRule ^webfilemanager/3859/(.*)$$1 [P]

where is a branding domain.

So, if one of the WebFileManager servers does not listen the port 1299, every second attempt to access the File Manager will throw the error 503.


  1. Make sure the firewall on the both WebFileManager nodes does not block incoming connections to the port TCP/1299
  2. Make sure Apache on the WebFileManager nodes is running and the port TCP/1299 is listened by it
  3. If IP address belongs to an Apache NG cluster, but WebFileManager is disabled on the cluster, perform the below steps:

    3.1. Go to OA > Infrastructure > Service Nodes > Web Clusters

    3.2. Click the cluster name, go to the Additional Services tab

    3.3. Set the checkbox next to WebFileManager, click Enable

    3.4. Wait until all related tasks are processed, repeat steps 3.1-3.2

    3.5. Set the checkbox next to WebFileManager, click Disable

after this the incorrect rule should be removed from the .htaccess file in the branding web directory.

5356b422f65bdad1c3e9edca5d74a1ae caea8340e2d186a540518d08602aa065 e12cea1d47a3125d335d68e6d4e15e07 dd79f16c76b9dca75205ab5e9f5465ea 1941880841f714e458ae4dc3d9f3062d

Email subscription for changes to this article
Save as PDF