[SOLVED] Wapt agent does not have the same version as the server

Share your tips or issues concerning the WAPT Console or WAPT Agent here
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
caudron26
Messages: 3
Registration: March 9, 2020 - 4:16 PM

March 9, 2020 - 4:20 PM

Hello,

the agent isn't updating to version 1.8. Here's what I have on the server:

WAPT Server version: 1.8.1
WAPT Agent version: 1.7.4.6165
WAPT Setup version: 1.8.1.6756
WAPT Deploy version: 1.8.1.6756
Database status: OK (1.7.6.6)

The console is also at version 1.7.4.6165
. If I close the console and reopen it, it asks me to create a new agent in version 1.8, but it ends up being yet another version of 1.7.4.
Do you have any idea what the problem might be?
I'm using Debian 9.
Thank you
Last edited by caudron26 on March 10, 2020 - 10:15, edited 1 time.
caudron26
Messages: 3
Registration: March 9, 2020 - 4:16 PM

March 9, 2020 - 4:41 PM

Additional clarification: the administration console is on a Windows 2016 server.
User avatar
jpele
Messages: 156
Registration: March 4, 2019 - 12:01
Location: Nantes

March 9, 2020 - 5:59 PM

Hello caudron26,

With each update, you need to manually install the WAPT console from your management machine, namely your WS2016. Following the console update, the agent generation will correctly use the new version 1.8.1.

Here is the documentation to follow: https://www.wapt.fr/fr/doc/wapt-configu ... pt-console

Regards,
Jimmy
caudron26
Messages: 3
Registration: March 9, 2020 - 4:16 PM

March 10, 2020 - 08:41

Thank you, that was exactly it!
I'd completely forgotten about that.
Thanks.

Have a good day
Locked