Skip to main content
Question

Unable to logon to Veeam One Client after upgrade to 13.1

  • August 3, 2026
  • 9 comments
  • 23 views
Y

Dear Community!

Last week, I updated my Veeam environment to version 13.1. After upgading my Veeam One installation, I’m no longer able to connect through the Veeam One Client, but from the WebUI it works fine.

I don’t know what is going on and I cannot contact support because I’m currently evaluating Veeam One product to see if it’s fit out needs.

Here is what I have from the Veeam.Reporter.log file:

03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService   -   -   -   -   - : -->TryGetWebGrpcCert
03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService   -   -   -   -   - : <--TryGetWebGrpcCert (in 0:00:00.0013216) Thumbprint: <removed for security>
03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService   -   -   -   -   - : -->GetOrCreateCommunicationCert
03.08.26 14:10:08 [INF] 0x10f8 - 45t 2580c CertProviderService   -   -   -   -   - : <--GetOrCreateCommunicationCert (in 0:00:00.000948) Cert: [<removed for security>]
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2580c Microsoft.AspNetCore.Routing.EndpointMiddleware : Executing endpoint '"gRPC - /GrpcReporterProto.GrpcReporterServiceProto/WebApiLogin"'
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c gRPC-Server   -   -   -   -   -   -   - : -->UnaryRequest "/GrpcReporterProto.GrpcReporterServiceProto/WebApiLogin" Peer:"ipv6:[::ffff:1.1.1.1]:60524" 
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WebApiAccessManager   -   -   -   -   - : -->Authorize {"fullUserName":"DOMAIN\\myuser","options":"InteractiveUserLogonWithWinauth, NoRefreshToken","ClientIpAddress":null,"ticketPurpose":"VeeamOneClient","limitedDomainAccess":false,"knownIdentity":""}
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : -->LoginBySidAndUsername Windows login by SID 'S-1-5-21-999999999-9999999999-9999999999-99999' for 'DOMAIN\myuser'
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : [TryLookupAccount]: 
		LookupAccountSid UserName: "DOMAIN\myuser"
			- lookup sid in "local" system for user "myuser@DOMAIN": sid found [S-1-5-21-999999999-9999999999-9999999999-99999] in domain "DOMAIN"
		LookupAccountName Sid: [S-1-5-21-999999999-9999999999-9999999999-99999]
			- lookup account in "local" system: account found DOMAIN\myuser

03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : -->TryGetUserRoleBySid DOMAIN\myuser (SID: S-1-5-21-999999999-9999999999-9999999999-99999) under "DOMAIN\service_user_account"
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : <--TryGetUserRoleBySid (in 0:00:00.018115) 
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : <--LoginBySidAndUsername (in 0:00:00.019467) Failed to get info for 'DOMAIN\myuser' (SID: S-1-5-21-999999999-9999999999-9999999999-99999): The server could not be contacted.
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : -->TryCollectInfo LoginIdentity: """, Id:None, Role:Unknown, SID:"S-1-5-21-999999999-9999999999-9999999999-99999" Authenticated  The server could not be contacted.", WindowsIdentity: "None", AcceptServiceUser: False, MustAuthorizeDomainAccess: False
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : -->TryGetUserRole  under "DOMAIN\service_user_account"
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : <--TryGetUserRole (in 0:00:00.0000005) 
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WindowsLoginProvider  -   -   -   -   - : <--TryCollectInfo (in 0:00:00.0003794) 
03.08.26 14:10:08 [INF] 0x10f8 - 91t 2581c WebApiAccessManager   -   -   -   -   - : Delaying failed authentication response by 0:00:02.9 to normalize timing to 0:00:03

Is anyone got this problem after updating to 13.1?

Thank you all and best regards,

Yanick

    9 comments

    coolsport00
    Forum|alt.badge.img+23
    • coolsport00
    • Veeam Legend
    • August 3, 2026

    Hi ​@Yanick Q. - Welcome to the Community.

    Did you upgrade VONE first, then VBR? Also, if memory serves, this is kinda normal. And, the VONE Guide shares something about this. I believe you have to “re-register” your VBR servers with VONE in the VONE WebUI Console > Configuration (Gear icon) > Data Collection. 

    Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
      Chris.Childerhose
      Forum|alt.badge.img+22
      • Chris.Childerhose
      • Veeam Legend, Veeam Vanguard
      • August 3, 2026

      No issue here with connection to VONE even with restoring my VSA after the upgrade borked it.

      You need to enable the remote management option and ensure the account does not have MFA enabled and is in the backup admin group via the console.  It should then connect.

      Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
        Y
        • Yanick Q.
        • Author
        • Comes here often
        • August 3, 2026

        Hi ​@coolsport00!

        Thanks for that quick reply!

        I’ve upgraded the VBR first then VONE. But the strange thing here is that I’m able to connect through WebUI https://voneserver.domain.com:1239. Only the console that has been installed on the server where the product is installed that did not work.

        I will search for how to “re-register” my VBR, hoping I won’t lose all the data I already have!

        Thank you very much!

        Regards,

        Yanick

         

          coolsport00
          Forum|alt.badge.img+23
          • coolsport00
          • Veeam Legend
          • August 3, 2026

          Let me expound on my comment. The issue I had was upgrading my VONE env from 12.3 > 13.0.1. If you were already on 13.x, you “should” be ok.

          Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
          coolsport00
          Forum|alt.badge.img+23
          • coolsport00
          • Veeam Legend
          • August 3, 2026

          Hi Yanick -

          Ok...keep us posted. Just be aware...the “register” issue I had was because I upgraded from 12.3 > 13.x. If you were already on 13.x, I’m not sure re-connecting VBR would do anything. But, you say your main issue is connecting to the VONE Client, right? Not sure registering your VBR to VONE via WebUI will work. Just check and make sure VBR shows as “healthy” in the VONE WebUI > Config > Data Collection section. If it is...not sure what to suggest next….

          Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
          Y
          • Yanick Q.
          • Author
          • Comes here often
          • August 3, 2026

          Hi ​@coolsport00 ,

          I just checked that out, and my server is “Healthy”. I upgraded from v13.0.2 to v.13.1.

          I will try to open a case, but I doubt they will provide me with assistance.

          If I got something, I will let you know, that may be useful!

          Regards!

          Yanick

            coolsport00
            Forum|alt.badge.img+23
            • coolsport00
            • Veeam Legend
            • August 3, 2026

            Ok, please keep us posted.

            Shane Williford - Veeam VMCA/VMCE+ | Veeam Legend | VUG Leader | VCP-DCV | Twitter: @coolsport00
            Y
            • Yanick Q.
            • Author
            • Comes here often
            • August 3, 2026

            No issue here with connection to VONE even with restoring my VSA after the upgrade borked it.

            You need to enable the remote management option and ensure the account does not have MFA enabled and is in the backup admin group via the console.  It should then connect.

            Hi Chris,

            I just noticed your reply!

            I don’t think the “remote management” was disabled, because I was able to logon before the upgrade and I was at version 13.0.2.

            My user is on the Admin group on my VBR server as well as in the “Veeam ONE Administrators” that has been created by the installation of VONE. However, my admin user has MFA enabled on VBR, but that was working before the upgrade. 

            Regards,

            Yanick

              Chris.Childerhose
              Forum|alt.badge.img+22
              • Chris.Childerhose
              • Veeam Legend, Veeam Vanguard
              • August 3, 2026

              No issue here with connection to VONE even with restoring my VSA after the upgrade borked it.

              You need to enable the remote management option and ensure the account does not have MFA enabled and is in the backup admin group via the console.  It should then connect.

              Hi Chris,

              I just noticed your reply!

              I don’t think the “remote management” was disabled, because I was able to logon before the upgrade and I was at version 13.0.2.

              My user is on the Admin group on my VBR server as well as in the “Veeam ONE Administrators” that has been created by the installation of VONE. However, my admin user has MFA enabled on VBR, but that was working before the upgrade. 

              Regards,

              Yanick

              Not sure as it should work then. I know you are evaluating it but you can still get support.  Might want to try that and see.  Seems odd the web UI works and not the other.

              Chris Childerhose (Enterprise Architect) - VMCE+ | VMCA | VMCE | VMCE-SP | Veeam Vanguard 8* | Veeam Legend 5* | VUG Canada Leader | vExpert 7* | Toronto VMUG Leader | VCAP-DCV/VCP-DCV/VCP-VVF | Object First Ace | Cisco Champion | Twitter: @cchilderhose | Blog Site – https://just-virtualization.tech
                Terms & ConditionsAccessibility statement