Skip to main content

Veeam Threat Hunter behind HTTP proxy

G
  • gordon
  • Not a newbie anymore
  • 1 comment

Just information for the Veeam community members.

If your Scan Backup Job with Veeam Threat Hunter ends with the error "Unable to perform scan: threat signatures database is missing" and your Veeam Mount server is behind an internet HTTP proxy, wait for the next minor version of VBR, or contact support, they have a temporary workaround.

Statement from support

At the moment, signature updates do not work properly when an HTTP proxy is used - this is a confirmed issue that was found recently, and it is planned to be addressed in the next minor patch 12.3.1.

    7 comments

    Chris.Childerhose
    Forum|alt.badge.img+21
    • Chris.Childerhose
    • Veeam Legend, Veeam Vanguard
    • 8427 comments
    • February 19, 2025

    That issue is interesting and nice to see that they will fix it in the next patch.  Thanks for sharing this with the community.

    Chris Childerhose - VMCA2024 | VMCE2023 | VMCE-SP2024 | Veeam Vanguard 8* | Veeam Legend 5* | vExpert 6* | VCAP-DCV/VCP-DCV | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
    dloseke
    Tommy O'Shea
    2 people like this
    • dloseke
      dloseke
    • Tommy O'Shea
      Tommy O'Shea
    dloseke
    Forum|alt.badge.img+8
    • dloseke
    • Veeam Vanguard
    • 1447 comments
    • February 19, 2025

    Good to know...thanks!

    Derek M. Loseke, Senior Systems Engineer | Veeam Legend 2022-2024 | VMSP/VMTSP | VCP6-DCV | VSP/VTSP | CCNA | https://technotesanddadjokes.com | @dloseke
    Chris.Childerhose
    Tommy O'Shea
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    lukas.k
    Forum|alt.badge.img+10
    • lukas.k
    • Veeam Vanguard
    • 191 comments
    • February 19, 2025

    Maybe I ran into this issue multiple times with some customers. I’m afraid this is not only the case with HTTP proxies but support is still investigating on this.

    Nice to see this addressed. :)

    LK | Veeam Vanguard | VUG Leader - Cyber Security Space | Security Specialist
    Chris.Childerhose
    Tommy O'Shea
    G
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    • G
      gordon
    T

    The mentioned temporary workaround:
    (quote Veeam support)

    Manually downloaded threat signatures from below link:

    https://storage2.veeam.com/v1/support?name=File_07597667_12ac6b1a87.zip

    Place them under C:\ProgramData\Veeam\Threat Hunter\Engines and then restart Veeam Threat Hunter service. Post this, backup scan should work.

    Certain cases, scan may fail because there were no successful automatic database updates for the last 14 days. To work around this, please create this registry value:

    Key: VTHUpdateFailureToleranceDays
    Location: HKEY LOCAL MACHINE\SOFTWARE\Veeam\Veeam Threat Hunter
    Type: DWORD
    Value: 1000

     

    For now, as long as automatic updates are not working, there will be a yellow warning in the scan session: "Failed to update signatures". But scan will work, and the session will end in green status.

    The proxy interoperability issue is going to be fixed in v12.3.1. So, once upgraded to v12.3.1, feel free to delete VTHUpdateFailureToleranceDays from the registry.

    Chris.Childerhose
    Tommy O'Shea
    G
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    • G
      gordon
    Egor Yakovlev
    Forum|alt.badge.img+1
    • Egor Yakovlev
    • Comes here often
    • 98 comments
    • March 10, 2025

    Hi all.

    Please, do not share support links from your cases in public - each case is individual and files working for one installation can render another installation corrupt. Additionally, that makes case tracking and fix prioritization much harder for us. Support team is ready to handle each case with utmost care and will provide a solution for each request.

     

     

    Chris.Childerhose
    Tommy O'Shea
    T
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    • T
      Thore Mangels
    T
    Egor Yakovlev wrote:

    Hi all.

    Please, do not share support links from your cases in public - each case is individual and files working for one installation can render another installation corrupt. Additionally, that makes case tracking and fix prioritization much harder for us. Support team is ready to handle each case with utmost care and will provide a solution for each request.

     

     

    Sorry about that. I will keep this in mind in the future.

    Chris.Childerhose
    Tommy O'Shea
    2 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    regnor
    Forum|alt.badge.img+14
    • regnor
    • Veeam MVP
    • 1349 comments
    • March 19, 2025

    The latest update from today, 12.3.1.1139 includes the fix and also a registry key to add a custom proxy.

    https://www.veeam.com/kb4696

    Max M. | Systems Engineer @Veeam | VMCE/VMCA | VeeaMVP 2023 | former Legend & Vanguard
    Chris.Childerhose
    Tommy O'Shea
    T
    3 people like this
    • Chris.Childerhose
      Chris.Childerhose
    • Tommy O'Shea
      Tommy O'Shea
    • T
      Thore Mangels

    Comment


    Terms & Conditions