Tranquil IT Forum

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

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

Hello,

OK, noted, thank you for your prompt response!

Cyril OLIVIER

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