Hello,
Following the installation of the WAPT 1.5 server, I am trying to create an agent via the console. Everything goes smoothly during compilation until I am prompted for the key. I enter it correctly, the compilation resumes, and then a dialog box opens with an error for which I cannot find a solution.
Error: An unhandled exception has occurred.
Unable to create WAPT update package.
ConnectionError: ("bad handshake: Error("bad handshake: Error(['SSL routines', 'ssl3_get_record', 'wrong version number')],)").
I tested access to https ://localhost:443 and it works.
The server is installed on a clean virtual machine. We were previously working with version 1.3 without any problems.
Awaiting a possible solution,
thank you.
Agent generation impossible (SSL error)
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
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Have you enabled https verification?
No, I haven't activated it... I don't understand.
Information: The server is installed in a school. We use the Kwartz interface, so I opened certain ports to allow access to WAPT. However, this worked with version 1.3. There may be some changes to make in the new version...
- cap1.JPG (61.44 KB) Viewed 6789 times
Information: The server is installed in a school. We use the Kwartz interface, so I opened certain ports to allow access to WAPT. However, this worked with version 1.3. There may be some changes to make in the new version...
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
To be perfectly honest, I haven't had the chance to test Wapt with Qwartz.
Generally, we recommend installing Wapt on "a server dedicated solely to this purpose"
https://www.wapt.fr/fr/doc/wapt_server_ ... quirements.
It seems to me that Qwartz listens on interface 443.
Generally, we recommend installing Wapt on "a server dedicated solely to this purpose"
https://www.wapt.fr/fr/doc/wapt_server_ ... quirements.
It seems to me that Qwartz listens on interface 443.
