KB4875 release notes and known issues

Summary

How to Configure HTTP Proxy for Windows-based Veeam Components KB ID: 4875 Product: Veeam Backup & Replication Veeam ONE Veeam Agent for Microsoft Windows Veeam Cloud Connect Published: 2026-07-14 Last Modified: 2026-09-18 Purpose This article explains how to configure an HTTP proxy for Windows-based Veeam components when the server must reach the internet through a proxy. It applies to Veeam products installed on Windows, including Veeam Backup & Replication, Veeam Cloud Connect, Veeam ONE, Veeam Service Provider Console, and Veeam Agent for Microsoft Windows . Note: This article covers Windows-based components only. For Linux-based components (the Veeam Software Appliance and JeOS-deployed appliances), see KB4807 . Connecting to a Veeam Cloud Connect Provider A tenant's Veeam Backup & Replication server cannot reach a Veeam Cloud Connect provider through an HTTP or HTTPS proxy. Cloud Connect traffic from the tenant's backup server is not HTTP(S)-based and therefore ignores proxy settings. Veeam Service Provider Console 9.3 and Later Starting with Veeam Service Provider Console 9.3, the WinHTTP, Internet Options, and environment variable proxy methods described below have no effect on the Veeam Service Provider Console Server, Web UI, REST API, or Management Agent clients. These components read their own HttpClient_UseProxy setting, which is disabled by default. For information about configuring HTTP proxy with Veeam Service Provider Console 9.3, review KB4930 . Solution Summary Configuring an HTTP proxy for Veeam components on Windows requires setting the proxy in up to three different places: WinHTTP is used by various Veeam components and is configured with netsh . WinINET (Internet Options) is used by components that rely on Windows Internet and is configured per user account. System-wide environment variables ( HTTP_PROXY , HTTPS_PROXY , and NO_PROXY ) are new in Veeam Backup & Replication 13. In Veeam Backup & Replication 13, many components were moved to modern .NET Core, and as such, they read their proxy configuration from environment variables first, falling back to WinINET (Internet Options) only when no environment variables are set. These components will not read the WinHTTP ( netsh ) configuration at all. HTTP Proxy Authentication Is Not Supported Proxy authentication is not supported. Because WinHTTP cannot authenticate to a proxy, the HTTP proxy must not require authentication. Use a proxy that permits connections without credentials, for example one that authorizes clients by source IP address. Configure WinHTTP Proxy System-Wide Configuration This change is system-wide and will affect all applications that use WinHTTP, including other third-party or Windows services that use WinHTTP (e.g., Windows Update). Check Current WinHTTP Proxy Settings This command will display the current WinHTTP settings: netsh winhttp show proxy Copy Set WinHTTP Proxy Settings This command can be used to set a WinHTTP proxy: netsh winhttp set proxy proxy-server= "<proxy>:<port>" Copy Note: Replace <proxy> and <port> in quotes with the actual proxy server's hostname or IP and the port it uses. For example, this command would set the proxy for all protocols to use proxy.domain.tld (192.168.111.111) port 8080: netsh winhttp set proxy proxy-server="192.168.111.111:8080" netsh winhttp set proxy proxy-server="proxy.domain.tld:8080" A more advanced example using a specific protocol and exclusions: netsh winhttp set proxy proxy-server="http=proxy.domain.tld:8080" bypass-list="*.labdomain.tld;*.devlab.tld" Reset WinHTTP Proxy This command can be used to reset the WinHTTP settings back to default (no proxy). netsh winhttp reset proxy Copy Configure Internet Options (WinINET) Proxy Proxy settings within Internet Options are configured per user. While the account you are logged in as may be able to access the internet through the proxy, the backup service account may not have access if that account hasn't had its internet connection settings c

Improvements and security content

• How to Configure HTTP Proxy for Windows-based Veeam Components KB ID: 4875 Product: Veeam Backup & Replication Veeam ONE Veeam Agent for Microsoft Windows Veeam Cloud Connect Published: 2026-07-14 Last Modified: 2026-09-18 Purpose This article explains how to configure an HTTP proxy for Windows-based Veeam components when the server must reach the internet through a proxy. It applies to Veeam products installed on Windows, including Veeam Backup & Replication, Veeam Cloud Connect, Veeam ONE, Veeam Service Provider Console, and Veeam Agent for Microsoft Windows . Note: This article covers Windows-based components only. For Linux-based components (the Veeam Software Appliance and JeOS-deployed appliances), see KB4807 . Connecting to a Veeam Cloud Connect Provider A tenant's Veeam Backup & Replication server cannot reach a Veeam Cloud Connect provider through an HTTP or HTTPS proxy. Cloud Connect traffic from the tenant's backup server is not HTTP(S)-based and therefore ignores proxy settings. Veeam Service Provider Console 9.3 and Later Starting with Veeam Service Provider Console 9.3, the WinHTTP, Internet Options, and environment variable proxy methods described below have no effect on the Veeam Service Provider Console Server, Web UI, REST API, or Management Agent clients. These components read their own HttpClient_UseProxy setting, which is disabled by default. For information about configuring HTTP proxy with Veeam Service Provider Console 9.3, review KB4930 . Solution Summary Configuring an HTTP proxy for Veeam components on Windows requires setting the proxy in up to three different places: WinHTTP is used by various Veeam components and is configured with netsh . WinINET (Internet Options) is used by components that rely on Windows Internet and is configured per user account. System-wide environment variables ( HTTP_PROXY , HTTPS_PROXY , and NO_PROXY ) are new in Veeam Backup & Replication 13. In Veeam Backup & Replication 13, many components were moved to modern .NET Core, and as such, they read their proxy configuration from environment variables first, falling back to WinINET (Internet Options) only when no environment variables are set. These components will not read the WinHTTP ( netsh ) configuration at all. HTTP Proxy Authentication Is Not Supported Proxy authentication is not supported. Because WinHTTP cannot authenticate to a proxy, the HTTP proxy must not require authentication. Use a proxy that permits connections without credentials, for example one that authorizes clients by source IP address. Configure WinHTTP Proxy System-Wide Configuration This change is system-wide and will affect all applications that use WinHTTP, including other third-party or Windows services that use WinHTTP (e.g., Windows Update). Check Current WinHTTP Proxy Settings This command will display the current WinHTTP settings: netsh winhttp show proxy Copy Set WinHTTP Proxy Settings This command can be used to set a WinHTTP proxy: netsh winhttp set proxy proxy-server= "<proxy>:<port>" Copy Note: Replace <proxy> and <port> in quotes with the actual proxy server's hostname or IP and the port it uses. For example, this command would set the proxy for all protocols to use proxy.domain.tld (192.168.111.111) port 8080: netsh winhttp set proxy proxy-server="192.168.111.111:8080" netsh winhttp set proxy proxy-server="proxy.domain.tld:8080" A more advanced example using a specific protocol and exclusions: netsh winhttp set proxy proxy-server="http=proxy.domain.tld:8080" bypass-list="*.labdomain.tld;*.devlab.tld" Reset WinHTTP Proxy This command can be used to reset the WinHTTP settings back to default (no proxy). netsh winhttp reset proxy Copy Configure Internet Options (WinINET) Proxy Proxy settings within Internet Options are configured per user. While the account you are logged in as may be able to access the internet through the proxy, the backup service account may not have access if that account hasn't had its internet connection settings c

Affected products and versions

Recommended action

Review the official publisher document before deployment.

Official publisher evidence