Page 1 of 1

Server and client communication

Published: February 6, 2018 - 1:52 PM
by DwarfDev
Hello everyone,

our setup is a WAPT server version 1.3.13.0.
Server OS: Linux.
Administration OS: Windows 7.


We are currently testing WAPT and have encountered some issues between the server and clients.

Initially, no problems were observed, as the console connects to the server successfully, allows packet sending to clients, and the clients appear to return valid status information. However, when I try to add a client to the server via the deployment agent, it no longer appears in the server's client list.

To resolve this issue of the client not registering with the server, I attempted to force registration using the command "wapt-get register".

At the same time, when I try to "build & upload" from PyScripter (running as administrator), nothing happens. I can only import packages using a build file and import them via the console with that file.

Regards,

Rémi

Re: Server and client communication

Published: February 6, 2018 - 4:52 PM
by sfonteneau
I assume you're using Debian?

Can you do a:

Code: Select all

dpkg -l |grep wapt


????

Re: Server and client communication

Published: February 6, 2018 - 4:59 PM
by DwarfDev
Hello,
Yes, we are using Debian for the Linux server.

Here is the result of the query:

`dpkg -l | grep wapt`

`ii tis-waptrepo 1.3.13.0 all server depot wapt local
ii tis-waptserver 1.3.13.0 all WAPT Server for linux
ii tis-waptsetup 1.3.13.0 all WAPT setup executable for Windows`

Re: Server and client communication

Published: February 6, 2018 - 5:16 PM
by sfonteneau
Hello,

if you are in the trial period, I advise you to switch directly to version 1.5:

https://www.wapt.fr/wapt-1.5/

Indeed, it is a Release Candidate version and it works much better than version 1.3.13!

Re: Server and client communication

Published: February 6, 2018 - 5:20 PM
by DwarfDev
Hello,

is this update only possible with a "clean" install or is a migration possible?

For this trial phase, we have 20 computers that rely on WAPT and we would like to keep the groups and packages
we have already created in the final version.