Page 1 of 1
[RESOLVED] The wapt configuration remains on version 1.7.4.x after upgrading to 1.8.0
Published: January 24, 2020 - 3:44 PM
by empbilly
My WAPT page shows:
WAPT Server Version: 1.8.0,
WAPT Agent Version: 1.7.4.6077,
WAPT Installer Version: 1.8.0.6641,
WAPT Deploy Version: 1.8.0.6641,
Database Status: OK (1.7.6.6),
Disk Space: 26% Free.
However, when I download the WAPT configuration file, it still shows version 1.7.4.x. The WAPT agent is also still showing version 1.7.4.x.
Is this a bug?
Re: The wapt configuration is still on version 1.7.4.x after upgrading to 1.8.0
Published: January 24, 2020 - 4:37 PM
by kguerineau
Hello,
To update the WAPT agent, you need to:
* Download the WAPTSetup (
https://www.wapt.fr/fr/doc/wapt-configu ... pt-console)
* Generate a new agent (
https://www.wapt.fr/fr/doc/wapt-configu ... wapt-agent).
This will change the WAPT agent version on your server to 1.8.0.x
Re: The wapt configuration is still on version 1.7.4.x after upgrading to 1.8.0
Published: January 25, 2020 - 04:06
by empbilly
Hello, did you give me the link to install the WAPT configuration, because you have the download link or for me to follow the instructions? If you follow the instructions, I've already done so.
- I upgraded to version 1.8
- I open the page wapt.mycompany.com and download the wapt configuration.
- Upon installation, it shows that it is version 1.7.4.x
The Wapt installer is not updating to version 1.8
This is what's happening.
Re: The wapt configuration is still on version 1.7.4.x after upgrading to 1.8.0
Published: January 27, 2020 - 11:10 AM
by kguerineau
Hello,
if WAPTSetup is still version 1.7.4, clear your browser cache and then restart the download. This should resolve the issue.
Re: The wapt configuration is still on version 1.7.4.x after upgrading to 1.8.0
Published: January 27, 2020 - 6:45 PM
by empbilly
Thanks kguerineau!! Works!!!
Re: [SOLVED] Wapt configuration still remains on version 1.7.4.x after upgrading to 1.8.0
Published: February 6, 2020 - 4:56 PM
by corriou
Same problem, same solution.
And since it's not something we tend to think of, it might be worth suggesting in the documentation.
Thanks again.