Skip to main content
Solved

Unable to connect to localhost Veeam B&R 12

  • July 2, 2026
  • 5 comments
  • 18 views

After update to VBR 12.3.2 I am unable to login.

The following error:

The socket connection was aborted. This could be cause by an error processing your message or a receive timeout being exceeded.  

I have restarted all veeam services, specifically veeam backup service.

All sql server (veeamxxx_ services have started.

However under SQL server config manager the sql server is running but the agent is stopped and I am unable to start that service ( grayed out).

 

TIA

Best answer by WilsonWilson

I just finally figured out that “localhost nor 127.0.0.1” would work.. Using FQDN fixed the login.

Thanks

5 comments

Chris.Childerhose
Forum|alt.badge.img+22

You will need to check the logs here - C:\ProgramData\Veeam

Otherwise I suggest a support ticket for this one.


  • Author
  • Not a newbie anymore
  • Answer
  • July 2, 2026

I just finally figured out that “localhost nor 127.0.0.1” would work.. Using FQDN fixed the login.

Thanks


Chris.Childerhose
Forum|alt.badge.img+22

Great to hear.


Forum|alt.badge.img+3
  • Influencer
  • July 3, 2026

Glad you solved it -- for some clarification, this can heavily depend on the server configuration / SQL instance configuration; for example, the backup server certificates may expect the FQDN for domained joined backup servers, SQL may be configured to only accept connections from specific hosts, etc.

In short, there’s no specific requirement from the Veeam side that you MUST use FQDN, but depending on quite a few factors Windows / SQL authentication may enforce such requirements. Like, my Veeam test lab uses LOCALHOST for everything, but it’s workgroup and SQL instances were specifically configured to allow connections from localhost / 127.0.0.1.

 


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

Some good tips and advice David.  Appreciate that as it makes sense.