[RESOLVED] WADS: wapt agent not registering

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
rlegrand
Messages: 10
Registration: June 30, 2026 - 3:37 PM

June 30, 2026 - 4:11 PM

Good morning,

I'm encountering a problem deploying Windows 11 with WADS; the OS deploys correctly, but the WAPT agent on the machine no longer registers with the server, and the post-installation script also fails to execute

I tested the deployment on two different machines, and I still encounter the same problem.

Below is the Wapt client log:

Code: Select all

2026-06-30 10:29:39,180 [waptcore WaptTaskManager 7500] CRITICAL Error merging Packages from wapt into db: 400 Client Error: Bad Request for url: https://srv-wapt.xxx.fr/wapt/Packages
Disabling Windows auto update service, using WaptWUA instead
2026-06-30 10:29:43,061 [waptcore WaptTaskManager 7500] WARNING Unable to update server status : 400 Client Error: Bad Request for url: https://srv-xxx.fr/update_host
2026-06-30 10:29:43,061 [waptcore WaptTaskManager 7500] CRITICAL Unable to update_server_status: None
2026-06-30 10:29:43,061 [wapttasks WaptTaskManager 7500] WARNING Update status failed, trying to register the computer...
2026-06-30 10:29:45,877 [waptcore WaptTaskManager 7500] CRITICAL Unable to register: Error sending registration data: status 403 content <html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>

2026-06-30 10:29:45,877 [wapttasks WaptTaskManager 7500] CRITICAL Unable to update server status: Error sending registration data: status 403 content <html>
<head><title>403 Forbidden</title></head>
<body>
<center><h1>403 Forbidden</h1></center>
<hr><center>nginx</center>
</body>
</html>

2026-06-30 10:29:57,387 [wapttasks SocketIOClient 3520] INFO Socketio connection params have changed. Socketio needs reconnect
2026-06-30 10:29:57,394 [wapttasks SocketIOClient 3520] INFO Creating socketio client: https://srv-xxx.fr:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\70bf4a6c-9463-4c39-bca3-4be5c2139a21.crt', 'C:\\Program Files (x86)\\wapt\\private\\70bf4a6c-9463-4c39-bca3-4be5c2139a21.pem') proxies: None verify_cert: False
2026-06-30 10:29:57,394 [wapttasks SocketIOClient 3520] INFO Connecting Socketio to https://srv-xxx.fr:443
2026-06-30 10:29:57,467 [waptws SocketIOClient 3520] WARNING Exception ConnectionError('Connection error'), waiting 33.76406250000001s before retrying
2026-06-30 10:30:31,250 [wapttasks SocketIOClient 3520] INFO Socketio connection params have changed. Socketio needs reconnect
2026-06-30 10:30:31,250 [wapttasks SocketIOClient 3520] INFO Creating socketio client: https://srv-xxx:443 client auth cert: ('C:\\Program Files (x86)\\wapt\\private\\70bf4a6c-9463-4c39-bca3-4be5c2139a21.crt', 'C:\\Program Files (x86)\\wapt\\private\\70bf4a6c-9463-4c39-bca3-4be5c2139a21.pem') proxies: None verify_cert: False
Thank you in advance for your help
High
User avatar
sfonteneau
WAPT Expert
Messages: 2339
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

July 1, 2026 - 5:32 PM

Hello

, could you please specify your registration method on the WAPT server?

Kerberos?
High
rlegrand
Messages: 10
Registration: June 30, 2026 - 3:37 PM

July 2, 2026 - 10:37

Hello,

Yes, Kerberos registration is enabled.

The Linux server is version 2.6.1.17834.

When I run `wapt-get register` on the client machine, it asks for credentials. I'm not sure why; I don't think this was happening before.

It worked fine previously, but I suspect Kerberos registration is no longer functioning.
High
User avatar
dcardon
WAPT Expert
Messages: 1970
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :
Contact dcardon

July 2, 2026 - 12:30

Hello rlegrand,

when you prepare the machine, do you select the template with AD integration and generate the DJoin file correctly? If so, do you have multiple Active Directories? And what is the propagation time for AD changes? It's possible that you created the DJoin file on one AD, but the workstation is connecting to a different one.

Regards,

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
High
rlegrand
Messages: 10
Registration: June 30, 2026 - 3:37 PM

July 2, 2026 - 1:59 PM

dcardon wrote: ↑July 2, 2026 - 12:30 PM Hello rlegrand,

when you prepare the machine, do you choose the template with AD integration and do you generate the DJoin file correctly? If so, do you have multiple Active Directories? And what is the propagation time for AD changes? It's possible that you created the DJoin file on one AD, but the workstation is connecting to a different AD.

Regards,

Denis
Yes, I'm using a template with domain integration.

The domain join is functional, the WAPT agent installs correctly, but the registration of the Wapt client on the server no longer works (the workstation does not appear in the console) and therefore the execution of the post install script commands cannot work ("Wapt-get" commands).
High
User avatar
sfonteneau
WAPT Expert
Messages: 2339
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

July 2, 2026 - 2:53 PM

Can you tell me what this returns on the WAPT server?

https://www.wapt.fr/fr/doc/wapt-securit ... -with-curl

Could you also tell me what type of server you have? Red Hat? Alma? Debian?
High
rlegrand
Messages: 10
Registration: June 30, 2026 - 3:37 PM

July 2, 2026 - 3:53 PM

sfonteneau wrote: ↑July 2, 2026 - 2:53 PM Can you indicate what this returns on the Wapt server?

https://www.wapt.fr/fr/doc/wapt-securit ... -with-curl

Code: Select all

root@SRV-WAPT:/home/wapt# kdestroy
root@SRV-WAPT:/home/wapt# kinit <user>
Password for <user>@<domaine>: 
root@SRV-WAPT:/home/wapt# klist
Ticket cache: FILE:/tmp/krb5cc_0
Default principal: <user>@<domaine>

Valid starting       Expires              Service principal
07/02/2026 15:35:34  07/03/2026 01:35:34  krbtgt/<domaine>@<domaine>
        renew until 07/03/2026 15:35:28
root@SRV-WAPT:/home/wapt# curl -v --negotiate -u : https://srv-wapt.<domaine>/api/v3/add_host_kerberos -k
* Host srv-wapt.<domaine>:443 was resolved.
* IPv6: (none)
* IPv4: 192.168.1.11
*   Trying 192.168.1.11:443...
* connect to 192.168.1.11 port 443 from 192.168.1.10 port 34656 failed: No route to host
* Failed to connect to srv-wapt.<domaine> port 443 after 3078 ms: Could not connect to server
* closing connection #0
curl: (7) Failed to connect to srv-wapt.<domaine> port 443 after 3078 ms: Could not connect to server
High
User avatar
sfonteneau
WAPT Expert
Messages: 2339
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

July 2, 2026 - 3:59 PM

Code: Select all

 
 connect to 192.168.1.11 port 443 from 192.168.1.10 port 34656 failed: No route to host
What is the server's IP address?
High
rlegrand
Messages: 10
Registration: June 30, 2026 - 3:37 PM

July 2, 2026 - 4:34 PM

sfonteneau wrote: ↑July 2, 2026 - 3:59 PM

Code: Select all

 
 connect to 192.168.1.11 port 443 from 192.168.1.10 port 34656 failed: No route to host
What is the server's IP address?
192.168.1.10
High
User avatar
sfonteneau
WAPT Expert
Messages: 2339
Registered: July 10, 2014 - 11:52 PM
Contact :
Contact Sfonteneau

July 2, 2026 - 4:44 PM

Isn't 192.168.1.11 listed in /etc/hosts? (bad configuration)

Kinit is trying to connect to 192.168.1.11...
High
Locked

Return to "WAPT Server"


  • To go further with WAPT