Error message:
Cloud licensing not available in your network
Cause:
ETS cloud licensing requires a direct internet connection to the KNX licensing servers. Proxy servers are not supported for cloud licensing due to the security architecture involved, which is designed to prevent tampering with the license validation process.
This means that even if your Windows system proxy is correctly configured and ETS uses it for other purposes (such as software updates, ETS App updates, catalog services, and news feeds), the cloud licensing component will not route its traffic through a proxy.
Why does ETS appear to ignore my proxy settings?
ETS uses the Windows system proxy settings for standard HTTP/HTTPS web-based communication. However, not all ETS network traffic is routed through the proxy. In particular:
Cloud licensing communicates directly with the KNX licensing servers and does not support operation through proxy environments.
ICMP traffic (connectivity checks): ETS sends ICMP requests to KNX servers before initiating actual connection requests in order to verify general internet availability. ICMP packets operate at the IP layer and are not forwarded through HTTP/HTTPS proxy servers. These checks include fallback mechanisms and do not prevent ETS from functioning correctly.
KNXnet/IP communication uses UDP, multicast, and IGMP for device discovery and communication. These protocols operate at the network layer and are not handled through standard Windows web proxy settings.
So while it is not correct to say that ETS ignores the Windows proxy entirely, it is also important to understand that several types of ETS network traffic — including cloud licensing — bypass the proxy by design.
Solution:
If your network environment requires all traffic to pass through a proxy server (e.g. in corporate networks with strict firewall policies), cloud licensing will not work. You have two options:
Adjust your network policies to allow a direct connection from the ETS machine to the KNX servers. See ETS6: Internet connection for the required addresses and ports.
Use a hardware dongle license instead. Dongle-based licensing does not require an internet connection for license validation and is therefore fully compatible with proxy and restricted network environments. See Dongle-based licensing for details.