Skip to main content

Caution: 13.1: Do not upgrade if you're using explicit internet proxy

  • August 4, 2026
  • 9 comments
  • 50 views

So it's very simple, our backup server (infrastructure appliance) had a proxy server configured for access to Internet (in order to fetch updates etc.)

Everything good in 13.0.

In 13.1 it seems to be trying to use internet proxy to connect to anything http(s), even “localhost”. Goes without saying that Backup server doesn't even properly start (system services can't connect to local identity service bc that sends them to internet proxy).

After defining proxy exceptions for localhost etc., connections to data movers still fail, again because those connections attempt to go through internet proxy.

Case is open with support. Reverted to 13.0. Careful!

9 comments

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

Thanks for sharing this.  Be interested to see what support says on the matter.


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

Interesting issue there ​@Jeronimo . Also curious to hear what Support says about this.


  • Author
  • August 5, 2026

@Chris.Childerhose ​@coolsport00 

Initially they told me that I should put localhost etc in the proxy exception list.

That solves the problem not being able to talk to local services like identity service, but it still tries to connect to many things outside (i.e. HTTP(s) on LAN) through the internet proxy. Which of course won't work to connect to data movers etc. That's where we’re at and I’ll stop doing QA for them now ;)


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

Yeah hopefully they will get it sorted for you must be something that changed recently maybe.  Keep us posted.


  • Author
  • August 5, 2026

something that changed recently maybe

Yeah, 13.1 would qualify as recent I guess 😁

From our inhouse devs I know that sometime they “just use” a different library to do the same stuff because it is “cooler” that way, and soon after, networking part of the app breaks down LOL

Well yeah, let’s give them a chance to react and see


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

One of a multitude of reasons why I don’t instantly go to the “newest” or “greatest” release of <insert-software-name-here>. I always let it play out. Now, v13.x has been out since Dec, but I was still waiting cuz have heard too many ‘hiccups’ happening with the new build, even on Windows (which is what I will be going to 1st eventually). 

Still...curious what Support comes back with. Keep us posted.


  • Author
  • August 5, 2026

Sure, however in my reasoning 13.0 was the “beta” release and 13.1 would have just made it better and cleaned out the remaining bugs. 😂

We’ll see.


Iams3le
Forum|alt.badge.img+15
  • August 5, 2026

@Chris.Childerhose ​@coolsport00 

Initially they told me that I should put localhost etc in the proxy exception list.

That solves the problem not being able to talk to local services like identity service, but it still tries to connect to many things outside (i.e. HTTP(s) on LAN) through the internet proxy. Which of course won't work to connect to data movers etc. That's where we’re at and I’ll stop doing QA for them now ;)

From what you have explained so far, I would lean toward a Veeam 13.1 proxy-handling regression. Out of curiosity, what type of proxy are you using (explicit forward proxy, or transparent proxy etc.)?


  • Author
  • August 5, 2026

@Chris.Childerhose ​@coolsport00 

Initially they told me that I should put localhost etc in the proxy exception list.

That solves the problem not being able to talk to local services like identity service, but it still tries to connect to many things outside (i.e. HTTP(s) on LAN) through the internet proxy. Which of course won't work to connect to data movers etc. That's where we’re at and I’ll stop doing QA for them now ;)

From what you have explained so far, I would lean toward a Veeam 13.1 proxy-handling regression. Out of curiosity, what type of proxy are you using (explicit forward proxy, or transparent proxy etc.)?

Not sure I understand the question? Obviously it’s an explicit proxy since a transparent proxy is transparent by definition i.e. the application knows nothing about it and you don’t have to configure it in the application hence the application cannot make a bad choice where to send traffic.

BTW the title of the post already mentions it ;)