Hello everyone,
for the past few days my wapt-2.2.1.11899 Discovery console on Windows 10 (with a wapt server of the same version on Windows Server 2016) has been crashing 20 seconds after clicking on the "Private Repository" tab.
I've run wapt-scanpackages.bat on the server (it finished without errors), rebooted the server... but nothing works; my console closes every time I try to access the local repository.
There's no unusual information in the console or server logs.
I'm sending out a message in a bottle.
Thanks,
Olivier
[SOLVED] Console crash
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
-
dcardon
- WAPT Expert
- Messages: 1932
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Olivier,
I believe this is related to the retrieval of new versions available on LUTI, which wasn't correctly handling the proxy configuration in version 2.2. The change in behavior would then be due to a change in the network configuration.
If this is indeed the bug, it has been fixed in subsequent versions of WAPT.
That said, WAPT version 2.2 is no longer supported as of January 2024 [1]. Upgrading is strongly recommended.
Best regards,
Denis
[1] https://www.wapt.fr/en/doc-2.5/wapt-enterprise.html
I believe this is related to the retrieval of new versions available on LUTI, which wasn't correctly handling the proxy configuration in version 2.2. The change in behavior would then be due to a change in the network configuration.
If this is indeed the bug, it has been fixed in subsequent versions of WAPT.
That said, WAPT version 2.2 is no longer supported as of January 2024 [1]. Upgrading is strongly recommended.
Best regards,
Denis
[1] https://www.wapt.fr/en/doc-2.5/wapt-enterprise.html
Denis Cardon - Tranquil IT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
Share your experiences on WAPT! Send us your blog and article URLs in the "Your Opinion of the forum, and we'll feature them on the WAPT
