Why Is Core Receiving HTTP 403 or Timeout Errors when downloading engine updates from OCM?

Issue

You may see log messages similar to the following in your Core system:

HTML
Copy

Cause

These messages usually mean that Core is having trouble connecting to OCM (OPSWAT Central Management). It may be caused by:

  • Network timeout or proxy issues
  • Port 9000/tcp being blocked
  • Restrictions in your firewall or proxy

Solution

Please check the following:

  1. Proxy or Network Settings Make sure your network allows Core to connect to the OCM server. If you're using a proxy, verify that it allows traffic to the OCM address on port 9000/tcp.
  2. Firewall Rules Ensure port 9000/tcp is open between Core and OCM. This is required for downloading updates and descriptors.
  3. More Info on Ports For a full list of ports used by OCM, see the documentation here: Recommended System Requirements - OPSWAT Central Management v7 - Legacy.

If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
What do I do when licensed engines are not detected despite active licenses?
On This Page
Why Is Core Receiving HTTP 403 or Timeout Errors when downloading engine updates from OCM?IssueCauseSolution