Sign In with your
Trend Micro Account
Need Help?
Need More Help?

Create a technical support case if you need further support.

Unable to load widgets when Deep Security Manager is using Load Balancer

    • Updated:
    • 14 Mar 2020
    • Product/Version:
    • Deep Security 10.0
    • Deep Security 10.1
    • Deep Security 10.2
    • Deep Security 10.3
    • Deep Security 11.0
    • Platform:
    • N/A N/A

When Load Balancer is being used in Deep Security Manager (DSM), the widgets such as Computer Status and Ransomware Status may not appear and show the following instead:

Unable to load widget.

Unable to load widget


To resolve the issue, edit the Elastic Load Balancer (ELB) stickiness to 10 minutes (600 seconds) or higher value.

  1. On the web console, go to Load Balancers > Target Groups.
  2. Select the name and go to Description section.
  3. Under Port Configuration, click Edit stickiness.

    Edit stickiness

  4. Modify the value of Expiration Period to 600 seconds or higher.

    Set expiration

Make sure to use LB-generated cookie stickiness. App cookies do not work.

According to an AWS article, "the load balancer uses a special cookie to track the instance for each request to each listener. When the load balancer receives a request, it first checks to see if this cookie is present in the request. If so, the request is sent to the instance specified in the cookie. If there is no cookie, the load balancer chooses an instance based on the existing load balancing algorithm. A cookie is inserted into the response for binding subsequent requests from the same user to that instance. The stickiness policy configuration defines a cookie expiration, which establishes the duration of validity for each cookie. The load balancer does not refresh the expiry time of the cookie and does not check whether the cookie is expired before using it. After a cookie expires, the session is no longer sticky. The client should remove the cookie from its cookie store upon expiry."

The load balancer will not route requests to an instance that failed. Instead, it will re-route the request to a new healthy instance depending on the existing load balancing algorithm. The AWS article also mentioned that "if a client switches to a listener with a different backend port, stickiness is lost."

For more information, read the full article here: Configure Sticky Sessions for Your Classic Load Balancer.

Solution Id:
Did this article help you?

Thank you for your feedback!

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.

If you need additional help, you may try to contact the support team. Contact Support

To help us improve the quality of this article, please leave your email here so we can clarify further your feedback, if neccessary:
We will not send you spam or share your email address.

*This form is automated system. General questions, technical, sales, and product-related issues submitted through this form will not be answered.