some issues with the interface

[jcurnill]

Hello,
I'm currently installing the WAPT server and I'm having several issues with the console.
I've manually installed some workstations that appear correctly in the WAPT console, with the program downloaded from my server's IP interface (WAPT agent). However, some workstations appear as disconnected even though their IP addresses are responding.
In parallel, I performed an update (version 2.3.0.13470), and on some workstations, I can't install software with the message "Error when uploading package xxxx does not trust signer certificate xxxx".
My last problem is that I wanted to automate the installation using Group Policy. I followed the documentation, and it launches successfully. I even have the WAPT self-service software installed on the workstations, but they don't appear in my console.
After the update, do the programs update automatically, or do I need to replace them manually?
Thank you in advance for any advice you can give me.
Sincerely.

[flipflip]

Good morning,

In parallel I carried out an update (version 2.3.0.13470) and on some machines I cannot install software with the message Error when uploading package xxxx does not trusted signer certificate xxxx.

I'm encountering the same problem this morning, and upon examining my server logs, the waptserver.log file is filled with this message:

[waptserver ] WARNING Unable to trust supplied host certificate: EWaptCertificateUntrustedIssuer(None)

I would say there is a problem with the certificates but at the moment I have not found the cause.

Edit: A new version seems to fix this: https://www.wapt.fr/fr/doc/wapt-changel ... ht=trusted

[dcardon]

Hello Flipflip and jcurnill,

Regarding the message "Error when uploading package xxxx does not trust signer certificate xxxx.", you need to check if your public certificate (.crt) is indeed in the directory:

Code: Select all

c:\program files (x86)\wapt\ssl 

If on your management machine you had installed waptagent.exe on top of your waptsetup.exe installation, it is possible that the certificate was deleted during the upgrade from version 2.2.3 to version 2.3.

To explain the change, in version 2.2.3 the certificate was included during the regeneration of the innosetup installer, and therefore innosetup thought it should manage the file because it owned it. In version 2.3, the innosetup installer is no longer regenerated, but the configuration and certificate are added to the installer's certificate area. So, during the upgrade, if waptagent.exe had been installed on the management machine, innosetup considered itself the "owner" of the file, and therefore deleted it during the upgrade to 2.3.

Sincerely,

Denis

[flipflip]

Hello

Denis, that's exactly right. The agent is installed on the management machine, and I did indeed perform an update from 2.2.x to 2.3.x. I also confirm that the "c:\program Files(x86)\wapt\ssl" directory is empty.

I understand the logic, and I know the problem won't occur anymore with your new procedure, which is perfect.

One more question: how do I regenerate the certificate on the management machine?

Thank you.

[dcardon]

Hello Flipflip,

you don't need to regenerate the certificate (otherwise you'll also have to reinstall it on all client machines). The public certificate was created at the same time as the private key. They should normally be located side-by-side on your management machine (you can check your preferences to see where it is). Then copy it to c:\program files (x86)\wapt\ssl and that should fix it.

Alternatively, you can retrieve the certificate from any machine with your 2.2.3 agent still installed.

Regards,

Denis

[flipflip]

Denis,

In my c:\Users\Administrator\Private folder, I copied the *.crt files to the c:\Program Files (x86)\wapt\ssl folder. I rebooted my machine (just to be sure), launched the console, and tried adding a package (7-zip) to the host package on one of the machines in my network. When I clicked "Save":

[waptserver ] CRITICAL Error uploading package uuid 43087a2c-dcbb-4ace-b31f-a1e5dc9232e6: Host matching package 18CC6FF7-EF35-11EB-8B14-CC6FF6EE9E25 does not trusted signer certificate 26fb5658ee6cae79c64513df7cff5f4101d93f39db6e78500586baabdb1c633a
[waptserver ] CRITICAL upload_packages failed EWaptForbiddden('Host matching package 18CC6FF7-EF35-11EB-8B14-CC6FF6EE9E25 does not trusted signing certificate 26fb5658ee6cae79c64513df7cff5f4101d93f39db6e78500586baabdb1c633a')

I will not be able to retrieve the 2.2 certificates because all my machines have been upgraded to 2.3 via the agent update through the console.

Shouldn't I redeploy the agent via waptdeploy? I used this method for the initial installation by creating an innosetup package just to execute the correct command and then I pushed it to my network via the Kaspersky agent.

[jcurnill]

Hello
, same problem after copying the certificates...