[SOLVED] tis-remote-repo-http - Installation failed

Questions about WAPT Packaging / Requests and help regarding Wapt packages.
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
silica
Messages: 24
Registration: Nov 18, 2024 - 11:02

June 25, 2025 - 10:30

Finally, I managed to get the repositories to synchronize 100% by forcing this value in the repositories' wapt-get.ini file (not to mention wusa): `
remote_repo_dirs=wapt`.

Last step: I created my rules based on the agents' IP addresses, but the workstations are still using the main wapt server as the repository.
Is there a subtlety, a step I might have missed?
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

June 25, 2025 - 11:48

Hello,
you need to double-check that the DNS records are declared for each repository, and it's also possible that the HTTPS certificate verification is the issue. If it's a self-signed certificate, you should write the rule using HTTP rather than HTTPS.
Best regards,
Bertrand
User avatar
blemoigne
Messages: 178
Registration: July 17, 2020 - 11:29

June 25, 2025 - 11:51

If that doesn't solve the problem, you should provide us with the output of the following command on an agent that needs to connect to a secondary repository (as an administrator):

Code: Select all

wapt-get update -ldebug
silica
Messages: 24
Registration: Nov 18, 2024 - 11:02

June 25, 2025 - 3:42 PM

Hello and thank you for your reply

. The problem is now resolved.
I was missing `use_repo_rules=1` in the agent configuration.

This topic can be closed. :)
User avatar
dcardon
WAPT Expert
Messages: 1929
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 26, 2025 - 10:30

Hi Kevin,

thanks for the feedback :-) . I'm marking the topic as closed/resolved.

See you soon,

Denis
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Locked