Skip to main content
Question

VBR automatic license update fails with “Failed to update license key” error

  • Nov 3, 2026 8:09 AM UTC
  • 2 comments
  • 13 views

Forum|alt.badge.img

Hello Everyone,

On my VBR server, the automatic license update option is enabled, and Veeam attempts to update the license on its own in the background. During these attempts I get the following error:

[Error] Failed to update license key

What I’ve checked so far:

  • Firewall access from the VBR server to autolk.veeam.com:443 and vbr.butler.veeam.com:443 is allowed.
  • I verified with Test-NetConnection that both endpoints are reachable on port 443 (TcpTestSucceeded: True).

Despite this, the automatic license update still fails.

Has anyone run into this or knows a fix? Is there anything else besides port connectivity that I should check?

Thanks in advance.

2 comments

lukas.k
Forum|alt.badge.img+12
  • Influencer
  • Nov 3, 2026 8:17 AM UTC

Hi ​@yunus.tasci,

Make sure to also allow cert checks, that directly below the 443 to vbr.butler: https://helpcenter.veeam.com/docs/vbr/userguide/used_ports.html?ver=13

I often run into this when the cert checks are not possible. Hint from personal experience: The manual shows port 80, but depending on the individual config, port 443 may also be required.

 

Let us know if that helps. Keep in mind, you always can reach out to Veeam Support to get the logs investigated and pointed exactly to the issue.

 

Best regards

Lukas


Forum|alt.badge.img
  • Author
  • Comes here often
  • Nov 3, 2026 8:32 AM UTC

Hi ​@yunus.tasci,

Make sure to also allow cert checks, that directly below the 443 to vbr.butler: https://helpcenter.veeam.com/docs/vbr/userguide/used_ports.html?ver=13

I often run into this when the cert checks are not possible. Hint from personal experience: The manual shows port 80, but depending on the individual config, port 443 may also be required.

 

Let us know if that helps. Keep in mind, you always can reach out to Veeam Support to get the logs investigated and pointed exactly to the issue.

 

Best regards

Lukas

 

Hi ​@lukas.k 
Thank you for your valuable comment.

I understand that for the certificate checks, I need to allow *.ss2.us and *.amazontrust.com on TCP port 80 so the server can reach them. I’ll test this right away and report back.

Thanks again.

 

Best regards