VBR V13 Console Issues

[bschmidt]

I have noticed a few Veeam Backup & Replication V13 console issues. Has anyone else noticed these issues?

1) It's very slow to load when trying to connect to a VBR server

2) I get error "Failed to connect to backup server. The operation was cancelled". This happens 3-4 times before it eventually connects. This can take up to 5 mins before I can actually load the console which is not helpful.

3) If a user selects "Remember me" it will don't request a new MFA code. This is not a good security practice.

[TimoB]

Hi,
I had the same issues as you described in 1) and 2). Additionally, FLRs failed in most cases and were unable to mount restore points.
What actually helped in my support case has now been described in https://www.veeam.com/kb4819
In case that internet access on your VBR server is restricted, maybe this will help

[Mildur]

Hi B,

1.) Please ensure the backup server meets the system requirements and that you have applied all recommended anti-malware exclusions (KB1999). If the issue still occurs, please contact Customer Support so we can start a proper investigation.

2.) Same here—we’ll need a support case number to proceed.

3.) I just tested this in the Windows console: signed in the first time, selected “Remember me”, closed the console, and started a new session. I was prompted to confirm MFA. Please make sure you’re on Veeam 13.0.1 Patch 1 (13.0.1.1071). If MFA is still not requested, please open a case and share the case number with me.

In general, if you encounter an issue (including a performance issue), please contact our Customer Support team first. This is explained in our forum policy.
I’ll keep this topic for now, but next time it may be deleted if you report a technical issue without providing a support case number.

Thank you for understanding,
Fabian

[bschmidt]

This was my ticket open back in January - 07963251

[gmajestix]

I am also seeing issue with console it just stops working after a time. If I try to connect it says "Unexpected status code from SPNEGO request: 429".

[Mildur]

Thanks for the case number — that helped me find the internal R&D ticket. The support engineer on your case was correct: it’s currently with our development teams.

This situation can occur if the backup console is terminated unexpectedly (for example, if the process is killed via Task Manager). We plan to improve this behavior in one of the upcoming updates this year. I'll keep an eye on the internal ticket.

@gmajestix
May I ask for the case number? Just because you see an error message in the Web UI doesn’t necessarily mean your situation is related to this topic. Depending on the investigation in your case, I have to split your comment in to a new topic.

Best,
Fabian

[bschmidt]

The "Failed to connect to backup server. The operation was cancelled" error happens immediately when trying to connect. I don't cancel any task in the task manager when it happens.