Skip to main content
Answer

Kasten service is unavailable - VB connection validation failed

  • September 6, 2024
  • 1 comment
  • 42 views

I'm trying to add an Openshift hosted  k10(7.0.7) instance deployed via Operator to Veeam B&R(12.2.0.33.4). Dashboard is exposed correctly via Route and I am able to access it and login in my browser.

But when I try to add it in Veeam B&R server, an errror appears : Kasten service is unavailable.

 

When looking at Veeam Kasten plugin logs:

 

<2dac> Error    REQUEST FOR RESPONSE GET https://kasten.apps…../:443/k10/vbrintegrationapi-svc/v0/server
[06.09.2024 09:48:09] <6bc9> Error    VB connection validation failed
[06.09.2024 09:48:09] <6bc9> Error    Kasten service is unavailable. (System.Exception)

 

Has anyone encounetered something similar ?

Best answer by MattSlotten

VBR Kasten plugin log location on VBR: %PROGRAMDATA%\Veeam\Backup\Plugins\Kasten

A few things to try for anyone else experiencing this issue:

  1. Ensure that token authentication is enabled for Kasten (spec->auth->tokenAuth>enabled: true)
  2. Ensure you have a long-live token configured
    1. oc create token auth-svc --duration=$((365*24))h -n kasten-io

  3. If you’ve previously configured the plugin and connected to Kasten and reinstalled a new instance of Kasten, the VBR plugin has a cached GUID for the old Kasten instance, so simply delete the Kasten instance under Managed Servers in VBR and re-add

1 comment

Forum|alt.badge.img
  • New Here
  • Answer
  • October 20, 2025

VBR Kasten plugin log location on VBR: %PROGRAMDATA%\Veeam\Backup\Plugins\Kasten

A few things to try for anyone else experiencing this issue:

  1. Ensure that token authentication is enabled for Kasten (spec->auth->tokenAuth>enabled: true)
  2. Ensure you have a long-live token configured
    1. oc create token auth-svc --duration=$((365*24))h -n kasten-io

  3. If you’ve previously configured the plugin and connected to Kasten and reinstalled a new instance of Kasten, the VBR plugin has a cached GUID for the old Kasten instance, so simply delete the Kasten instance under Managed Servers in VBR and re-add