WAPT packages not visible on some VMs -- EWaptUnknownHost

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
Answer
Sami Khelil
Messages: 4
Registration: June 19, 2026 - 5:22 PM

June 19, 2026 - 5:28 PM

Hello,

For the past few weeks, I've been observing an intermittent problem on some VMs managed by our WAPT server: the packets assigned to these machines are no longer visible from the console.

The error observed in the WAPT server logs is:
Jun 19 08:44:04 XXXXX waptserver[1445]: 2026-06-19 08:44:04,804 [waptserver] CRITICAL update_host failed EWaptUnknownHost('Host certificate is not known for host 4ce6f7ed-0753-489a-8b4a-6ceaade49471, aborting').
The problem has occurred 3 to 4 times on 3 different VMs over the last 3 months.
It seems that the WAPT server no longer recognizes the client host's certificate.

Current workaround:
Running the following command from the affected machine resolves the issue: `wapt-get register

WAPTConsole Discovery version 2.6.1.17813`
User avatar
dcardon
WAPT Expert
Messages: 1978
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 25, 2026 - 6:05 PM

Hello Sami,

Could it be that the VMs in question were all generated using the same template on which WAPT had already been installed and registered?

If so, could you try the following command on the machines that are experiencing problems?

Code: Select all

 wapt-get reset-uuid
?

Sincerely,

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
Sami Khelil
Messages: 4
Registration: June 19, 2026 - 5:22 PM

June 25, 2026 - 9:00 PM

Thank you for your reply. Actually, I had an old WAPT 1.8 server that was working fine, and I installed a new WAPT 2.6 server. So I uninstalled the old agent (1.8) on the VMs, then installed the new agent (2.6). Everything is working correctly: the packages are updating, and I can add or remove them without any problems. I'll test it with the command `wapt-get reset-uuid` and let you know . Thanks.







Sami Khelil
Messages: 4
Registration: June 19, 2026 - 5:22 PM

June 30, 2026 - 3:04 PM

Good morning,

And there you have it, the problem has recurred, the VM's package list is indeed empty in the wapt console and I was able to see this error message under the wapt server.

Code: Select all

2026-06-30 09:00:08,415 [waptserver ] CRITICAL update_host failed EWaptUnknownHost('Host certificate in not known for host XXXXXXXXXXXXXXXXXX, aborting
The result of the command:

Code: Select all

C:\Program Files (x86)\wapt>wapt-get.exe reset-uuid
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
FATAL ERROR : [WinError 183] Impossible de créer un fichier déjà existant: 'C:\\Program Files (x86)\\wapt\\private\\db'

C:\Program Files (x86)\wapt>
User avatar
dcardon
WAPT Expert
Messages: 1978
Registration: June 18, 2014 - 09:58
Location: Saint Sébastien sur Loire
Contact :

June 30, 2026 - 3:55 PM

Hello Sami,
The result of the command:

Code: Select all

C:\Program Files (x86)\wapt>wapt-get.exe reset-uuid
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
FATAL ERROR : [WinError 183] Impossible de créer un fichier déjà existant: 'C:\\Program Files (x86)\\wapt\\private\\db'

C:\Program Files (x86)\wapt>
With what privileges? It needs to be launched with admin rights...

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
Sami Khelil
Messages: 4
Registration: June 19, 2026 - 5:22 PM

June 30, 2026 - 4:19 PM

Ah yes, sorry

Here is the result:

Code: Select all

C:\Program Files (x86)\wapt>wapt-get.exe reset-uuid
Using config file: C:\Program Files (x86)\wapt\wapt-get.ini
2026-06-30 10:15:33,840 CRITICAL Unable to update_server_status: Error on server:
EWaptMissingCertificate('You try to update status of an unknown host b8d0dd49-1302-430c-bd3c-d0fec31c4332 (domaine.XXX.XX). Please register first.')
2026-06-30 10:15:33,840 WARNING Update status failed, trying to register the computer...
New UUID: b8d0dd49-1302-430c-bd3c-d0fec31c4332

C:\Program Files (x86)\wapt>
That's why the solution I found was to add the command

Code: Select all

wapt-get register
in a planned task
Answer