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

Create a technical support case if you need further support.

Unable to download package in Deep Security Manager (DSM) local with error "HTTP/1.1 404 Not Found"

    • Updated:
    • 16 Oct 2020
    • Product/Version:
    • Deep Security 11.0
    • Deep Security 12.0
    • Deep Security 12.5
    • Deep Security 20.0
    • Platform:
Summary

When trying to install an agent on a machine, once it tries to get updates/download onto the Relay, the package cannot be found resulting to a "HTTP/1.1 404 Not found" error even though the equivalent package is already imported in the DSM local.

Using KernelSupport-Ubuntu_18.04-20.0.0-1176.x86-64.zip as an example, the moment this package is uploaded into the DSM local, it should also appear in the DSA directory under the relay folder:

  • Windows: C:\ProgramData\Trend Micro\Deep Security Agent\relay\www\dsa
  • Linux: /var/opt/ds_agent/relay/www/dsa

Uploaded package in DSM:

In the relay, the package is missing:

Details
Public
 
This procedure is mostly applicable when you have already restarted the relay service, conduct series of security updates and re-import of the packages into the console. Yet still, the relay won't get the package.
 

If the package (this may happen to both Windows and Linux) is already imported in the DSM (under Administation > Updates > Software > Local) and you still cannot download the right files, check the relay if the package exists there or not. Refer to the following locations:

  • Windows: C:\ProgramData\Trend Micro\Deep Security Agent\relay\www\dsa
  • Linux: /var/opt/ds_agent/relay/www/dsa

Download the package that you see on the DSM or download it from Trend Micro Download Center, and import the package on to those directories and restart the agent service.

Current Relay packages:

Manually import the package in that directory and restart the agent:

Result:

After doing so, for the affected agents, perform a send policy, check status, and/or a manual heartbeat. If all recommendations still do not fix the issue for the affected agents, perform a reactivation or reinstallation.

Premium
Internal
Partner
Rating:
Category:
Troubleshoot
Solution Id:
000278085
Feedback
Did this article help you?

Thank you for your feedback!

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.

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.