Tranquil IT Forum

Hi Marc,

does the deployment work on the primary site (without a secondary repository)? Does it work if you disable the secondary repository rules for the machine/subnet in question?

Regarding the secondary repository, is it a Windows or Linux machine? Is it using an nginx server or a wapthttpserver?

Which version of wapt?

Regards,

Denis

Hello,
we tried directly on the LAN where the WAPT 2.5 server is located on a Linux server.
We used wapttftpserver for TFTP and nginx for HTTP.
Nothing happens on the main site.

On the secondary repository, we are using a Windows 10 machine with a WAPTHttpServer Remote Repository installed since yesterday.

Today, our tests are being conducted from the secondary repository site.
That's all the additional information.
Thank you

Hello,
we're making progress with our installation.
We've reached the blue screen: IPXE boot menu For WAPT Deployment.
After selecting Register host (winpe x64),
we chose IPXE, and the PC reappeared in the console.

Then we get stuck on a command prompt window: VerifyCert: 0
No IP address found.
Running ipconfig gives us: Windows IP Configuration.

The command in the previous window was: start cmd /kx:\dlls\wgetwads64.exe --verify-cert=0 --server_url=https://xxx-xxx-wapt.

During the download, there was indeed an IP address in the correct VLAN.
We're looking to move on to the next step...
Thank you.

Hello

, there are actually two things:

IPXE and WinPE.

In your case, IPXE correctly detects the network card. However, WinPE doesn't seem to detect it.

You would need to add the network card drivers to your WinPE installation. See:
https://www.wapt.fr/fr/doc/wapt-wads.ht ... inpe-files

Hello,
we are indeed making progress; loading the network driver has allowed us to move to the next step.
On the server's LAN test, we reach the Welcome WADS task #3 window
and an error message, then nothing:
Host data verification failed: no signer_certificate in data.


On the secondary repository server:
error getting wads executable from server: THttpClientSocket.Wget: xx.xx.xx.xx:443/wads/wads64.exe failed as 404 Not Found.

The test downloading the wads64.exe file via a browser works over HTTP, but not over HTTPS.
In both cases, I signed the .exe files on the server via the console. That's

where we're at for now.

Vercingetorix wrote: ↑Oct 14, 2024 - 11:53 error getting wads executable from server: THttpClientSocket.Wget: xx.xx.xx.xx:443/wads/wads64.exe failed as 404 Not Found
The test downloading the wads64.exe file via a browser works in http, but not in https.

Using HTTP but not HTTPS?

If you just go to:

https://xx.xx.xx.xx

What does that answer?

On the secondary server with the error:
https://ip_secondary_server/
WAPTHttpServer Server Error 404

HTTP 404 Not Found

Wrong route
mORMot 2

On the primary server, after entering the WAPT Server password
: ENTERPRISE

to summarize

, this works:

http://ip_serveur_secondaire/wads/wads64.exe

but not this:
https://ip_serveur_secondaire/wads/wads64.exe.

Strange, yet it's the same configuration.

Hello,
since the configuration being used is that of the secondary repository declaration in the wapt console,
we changed the HTTPS address to http://xx.xx.xx.xx/wapt.
And now we're getting the same error:
Error getting wads executable from server: THttpClientSocket.WGet: xx.xx.xx.xx:80/wads/wads64.exe failed as HTTP Error 404 - Not Found.

The same error, except 80 instead of 443.

This is strangely similar to the following topic: viewtopic.php?t=3161.

Have a good day.

Hello,
we were advised to use wapt-remote-repo-http instead of tis-remote-repo-nginx.
However, when using wads on a secondary repository, we were getting the error message: "
Error getting wads executable from server: THttpClientSocket.WGet: xx.xx.xx.xx:80/wads/wads64.exe failed as HTTP Error 404 - Not Found"
We therefore reverted to nginx and we no longer encounter this error.

We can now mark the topic as [RESOLVED]
. Have a good day.