I followed the instructions correctly, but there's no change for me; the setup and agent are still at 1.5.13. I don't understand... I'll wait for the next version!
[BETA] WAPT 1.5
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
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
-
joris.remandet
- Messages: 15
- Registration: January 16, 2018 - 6:29 PM
Even when waptconsole.exe and the wapt installation folder are excluded, it automatically ejects the executable. 
Hi,
I've had a strange issue since version 1.5.1.15. Some agents have correctly installed the wapt-upgrade 1.5.1.15 package, but in the wapt console, the wapt version column still shows 1.5.1.8...
And another odd thing is that some clients, while upgrading to 1.5.1.15, have corrupted themselves by removing Python libraries, making it impossible to restart the wapt service...
Have you ever seen this kind of behavior?
Thanks in advance,
I've had a strange issue since version 1.5.1.15. Some agents have correctly installed the wapt-upgrade 1.5.1.15 package, but in the wapt console, the wapt version column still shows 1.5.1.8...
And another odd thing is that some clients, while upgrading to 1.5.1.15, have corrupted themselves by removing Python libraries, making it impossible to restart the wapt service...
Have you ever seen this kind of behavior?
Thanks in advance,
Nobody? It happened to me again this morning.
guigeek wrote: ↑Jan 23, 2018 - 5:14 PM Hi,
I've had a strange issue since version 1.5.1.15. Some agents have correctly installed the wapt-upgrade 1.5.1.15 package, but in the wapt console, the wapt version column still shows 1.5.1.8...
And another strange thing: some clients, when upgrading to 1.5.1.15, corrupted themselves by removing Python libraries, making it impossible to restart the wapt service...
Have you ever seen this kind of behavior?
Thanks in advance,
Hello,
what is the correct order of operations when upgrading from version 1.3 to 1.5 using remote repositories?
We have set up a test WAPT infrastructure with a main central server and 12 remote repositories, currently at version 1.3.13.
Should we first update the tis-waptrepo package on all remote repositories and then update the main server?
Should we disable SyncThing replication beforehand? Or something else?
Thomas
what is the correct order of operations when upgrading from version 1.3 to 1.5 using remote repositories?
We have set up a test WAPT infrastructure with a main central server and 12 remote repositories, currently at version 1.3.13.
Should we first update the tis-waptrepo package on all remote repositories and then update the main server?
Should we disable SyncThing replication beforehand? Or something else?
Thomas
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Hello
, the documentation describes installing tis-waptrepo to install Apache.
In your case, you don't need to do anything on the remote repositories.
HOWEVER, BEWARE!
The migration from 1.3 to 1.5 requires all WAPT packages to be re-signed. This will generate traffic on all your remote repositories, so be mindful of your bandwidth!
Also, be aware that if you enable HTTPS certificate verification in version 1.5, you will need to replace the HTTPS certificates of the remote repositories.
, the documentation describes installing tis-waptrepo to install Apache.
In your case, you don't need to do anything on the remote repositories.
HOWEVER, BEWARE!
The migration from 1.3 to 1.5 requires all WAPT packages to be re-signed. This will generate traffic on all your remote repositories, so be mindful of your bandwidth!
Also, be aware that if you enable HTTPS certificate verification in version 1.5, you will need to replace the HTTPS certificates of the remote repositories.
Good morning,sfonteneau wrote: ↑Feb 9, 2018 - 11:31 AM Hello,
The documentation says to install tis-waptrepo to install Apache.
In your case, you don't need to do anything on the remote repositories.
HOWEVER, BEWARE!
The migration from 1.3 to 1.5 requires that all WAPT packages be re-signed. This will generate traffic on all your remote repositories, so be careful with your bandwidth!
Also, be aware that if you enable HTTPS certificate verification in version 1.5, you will need to replace the HTTPS certificates of the remote repositories.
Thank you for your response.
Yes, I had noted that all packages needed to be resigned, and that this would therefore result in a complete replication
So there's no need to update the tis-waptrepo on the repo, ok, however they will remain at version 1.3.13, no problem?
Okay for the HTTPS certificate, I'll look into it more closely. Is there any documentation or tutorial for it?
THANKS
I don't want to spoil anything, but it's 21 days 
until the next release. The links are being updated.
- Alexandre
until the next release. The links are being updated.
- Alexandre
