Skip to main content
Question

About deploy pve worker on the air-gapped envirment

  • August 30, 2026
  • 6 comments
  • 29 views

Hi Everyone,

 

I installed Veeam 13.1 on Windows Server 2022 without joining an AD domain and in an environment without internet access. I used IP addresses when adding the PVE9.2, but when I deployed the workers, the installation failed with the error “Veeam Updater is unavailable.” Later, I set up DNS forward and reverse lookups for the PVE and worker IPs, but the same error persisted. I unchecked the “Check for updates online” option for the workers.

Does Veeam require an internet connection for the worker to install packages?

 

Translated with DeepL.com (free version)

6 comments

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

Hi ​@nsofl.chen - no, Veeam doesn’t require internet access for worker installs. See below reference in teh Uesr Guide on Architecture for PVE & Veeam:

https://helpcenter.veeam.com/docs/vbr/userguide/pve_infrastructure_components.html?ver=13

There is a somewhat similar thread about Updater Service on v13.1 below:

Maybe reach out to Support, and monitor that post for resolution to see if what Support does helps your issue as well.

Best.


  • Author
  • Comes here often
  • August 30, 2026

@coolsport00 
 

Thank you,

After reinstalling version 13.0.3.63, I’ve been using the backup LAN IP for everything without configuring any DNS A records or the hosts file. The worker installed and tested successfully, and backups are working normally.

I wonder if version 13.1.1.18 might have introduced some restrictions?


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

That's possible. Only Support would be able to answer that. 

Glad you at least got back to a working state. 


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • August 31, 2026

Hi ​@nsofl.chen! During the V13.1 beta the update servers weren’t available but the worker deployment proceeded after the update ran into a time out. I just tried it again in my lab with the latest build and the deployment succeeded. Could you post a screenshot of your error message or share the full message?


  • Author
  • Comes here often
  • September 1, 2026

Hi ​@regnor 

This error occurs in version 13.1. I reinstalled version 13.0, and it worked fine, but after I updated to 13.1.0.411 or 118, the error reappeared.

 


regnor
Forum|alt.badge.img+14
  • Veeam MVP
  • September 1, 2026

This looks like a different issue than the Veeam Update Repositories not being reachable. Is there a firewall or proxy between the workers and the Veeam Backup & Replication Server?