V13 - Unable to Login to console - Unable to perform OAuth authorization: interaction_required

[telnetrix]

Yesterday we had normal access to the local member server running Veeam backup server v13.
Today we get the message: "Failed to connect to the backup server: Unable to perform OAuth authorization: interaction_required."

We only use local user accounts for access, with no 2FA/OAuth provider.

I do not see any references to this issue online.

Case ID#08068106

[telnetrix]

Got a response to ticket--posting the response here, as it did resolve our issue.

Please try the following steps below:

Log in with username and password instead of single sign-on

If already using the username and password method and yet the same behavior is observed, make sure the "Remember me" box is checked. The first attempt after this will fail but the next time around, the login will be successful.

[sjameel]

Doesn't really help if you have a secure environment where you can't login with a username/password (ie. smartcard login only).

[HannesK]

Hello,
very likely solution: Uninstall the console and re-install it including all updates.

Very likely it's that for unknown reason, the C:\Program Files\Veeam\Backup and Replication\Console\Veeam.Backup.UI.Launcher.dll did not update correctly. If you check the properties of that file and check the Product Version / File Version, then you see 13.0.1.180 instead of 13.0.1.2067

Second thing to check C:\Users\your user\AppData\Local\Veeam\Backup\Utils\Util.ClientLauncher.log: this file must have the following log entries

Code: Select all

"Cookie container is successfully initialized from the start"
"Cookie container is successfully initialized"

If these log entries do not exist, then the error message from above can show up

Best regards
Hannes

[Servior]

If that is the fix, why isn’t that communicated in a support ticket?

They still post the workaround (which works) and telling it will be fixed in a future update. The last update did not include the fix.

[vitami]

I've been told the same (Case #08062157) - will be fixed in a future update. No logs were requested from the client where the console runs.
However, a complete console reinstall did not fix the issue. I think it started happening after updating the PVE Plugin (just the plugin) to latest.

The log 'C:\Users\your user\AppData\Local\Veeam\Backup\Utils\Util.ClientLauncher.log' does not contain the entries HannesK describes, instead on sytem boot it logs

Code: Select all

[25.04.2026 11:40:56] <06> Error    [HaFailoverPerformer] Failed to check that that HA enabled
[25.04.2026 11:40:56] <06> Error    Method 'UpdateCockpitIntegrationStatusFile' in type 'Veeam.Backup.Interaction.HA.Grpc.VbrHaPrimaryServiceProxy' from assembly 'Veeam.Backup.Interaction.HA.Grpc, Version=13.0.1.0, Culture=neutral, PublicKeyToken=null' does not have an implementation.

C:\Program Files\Veeam\Backup and Replication\Console\Veeam.Backup.UI.Launcher.dll is on version 13.0.1.180

I previously asked why we cannot disable the remember me option as it is bad practice. And now I have to explicitly tell my coleagues to enable it so they can login at all. I'm not happy with the console since v13, and we can't use the web UI because pve is not integrated yet.

[HannesK]

Hello,

C:\Program Files\Veeam\Backup and Replication\Console\Veeam.Backup.UI.Launcher.dll is on version 13.0.1.180

This means, that the latest update was not applied. Something in the re-install / update process failed for unknown reason.

The thing is, that the issue is fixed already (at least all scenarios we are aware off) and the problem is the outdated DLL. Yes, installing the next update should also fix it, because then the DLL would be replaced again.

We had the same issue in one of the labs I maintain. Randomly, logins worked, but most of them failed. It made no reproduceable difference to use "sign in as current user" or "remember me" or "local account" vs. "domain account". It was solved by re-installing the console and installing the 13.0.1.2067 patch on top. Once the Veeam.Backup.UI.Launcher.dll was on 13.0.1.2067, it worked fine.

Best regards
Hannes

[vitami]

Hello Hannes

I just reinstalled the console again (removed it completely, rebooted, installed 13.0.1.180, started it, logged in and applied the patch) but the Veeam.Backup.UI.Launcher.dll is still on 13.0.1.180 and the issue persists.
Is the Proxmox VE Plugin on your test machine also on v13.3.1.7?