Alternating between primary and secondary customer deposits.

Share your tips or issues concerning the WAPT Console or WAPT Agent here
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Answer
cedric_974
Messages: 11
Registration: Nov 13, 2025 - 05:42

February 11, 2026 - 08:13

Hello,

I'm going to reuse part of one of my posts to avoid rewriting everything. :D

I'm connecting to a corporate console on a remote primary repository (WAN) which is using HTTPS, which I'll call Principal01.fr.

Principal01.fr has the IP address 192.1.1.3.
A GPO on a Windows domain deployed the WAPT agent on the machines with the following settings in wapt-get.ini:
repo_url=//Principal01.fr/wapt
wapt_server=https:/Principal01.fr

I then set up a secondary repository (LAN) using HTTP, which I'll call Secondary02.fr, and which seems to be working correctly: it synchronizes properly with Principal01.fr.
Secondary02.fr has the IP address 192.168.1.3.

I added a rule based on clients' IP addresses:
If the client belongs to the 192.168.1.0/24 network, then the repository used should be http://Secondaire02.fr/wapt
. I checked WAPT, WUA, and WADS and disabled fallback.

This is where things get complicated. Randomly, on my console (on Principal01.fr), when I go to the Inventory section and select a client from the 192.168.1.0/24 range, in the Repositories tab, I sometimes see the primary repository and sometimes the secondary repository. I can't find an explanation for why sometimes my clients stop connecting to the secondary repository.

Thank you for your help.
High
Answer

Return to "WAPT usage (Console, Agent) / WAPT usage (Console, Agent)"


  • To go further with WAPT