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
[RESOLVED] WAD Deployment - No more network devices
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
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
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
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
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
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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
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
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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.
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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
, 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
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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.
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Using HTTP but not HTTPS?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.
If you just go to:
https://xx.xx.xx.xx
What does that answer?
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
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.
, 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.
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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.
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.
-
Vercingetorix
- Messages: 36
- Registration: Sep 19, 2024 - 09:09
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.
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.
