OS deployment from secondary repository (ISO downloaded from main site)

Questions about WAPT Server / Requests and help related to the WAPT server
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
Locked
C.Olivier
Messages: 2
Registration: January 24, 2023 - 2:36 PM

January 24, 2023 - 3:16 PM

Configuration:

WAPT Enterprise version: 2.3.0
Server OS: Debian Bulleyes
WAPT server behind a reverse proxy.
Secondary repository OS (wapt-host, wapt, waptwua, wads): Debian Bulleyes
Administration machine OS: Windows 10


Good morning,

I am encountering a small problem when deploying OS from a secondary repository.
I should point out that my main server is behind a reverse proxy, everything is OK except for the ISO download during deployment which is not happening on the correct server.
The repository is properly synchronized and all files on the web server are present and accessible.

Let me explain:
During PXE boot and deployment, the downloads "/wads/winpe/x64/media/*" and driver packages are successfully completed from the correct secondary repository, after a "POST /api/v3/get_wads_config" request from my main server via the reverse proxy.

I deduce that this "POST /api/v3/get_wads_config" tells the client being deployed to redirect to the secondary repository using https.

However, this request does not appear when downloading the ISO, and the ISO is downloaded from the main repository.

For my part, I successfully fixed this issue by setting up a conditional redirection at the reverse proxy level for the wads folder based on the client's CIDR.

location /wads {
if ($Ip_CIDR) {
return 301 http://url_de_mon_depot$request_uri;
}
proxy_pass http://ip_de_mon_serveur_maine:80;
}
However, this does not seem consistent with the rest of the process; is this normal, or have I forgotten something?

Thank you in advance for your clarification
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 25, 2023 - 6:14 PM

Hello and thank you for your feedback.

Indeed, there is a problem in the latest version. A regression has crept into the secondary WADs repository.

We released a fix today and will soon release a new version that corrects this.

Simon Fonteneau
C.Olivier
Messages: 2
Registration: January 24, 2023 - 2:36 PM

January 26, 2023 - 09:46

Hello,

OK, noted, thank you for your prompt response!

Cyril OLIVIER
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

January 26, 2023 - 3:13 PM

Hello!

We just released a nightly build that includes this patch.

Available here: https://wapt.tranquil.it/wapt/nightly/w ... 6/?C=M&O=D
Locked