Hi,
I just wanted to know if any of you have experienced this problem before?
I don't know where else to look.
Thanks
Socket error #10061 Connection Refused.
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
In the console > Tools > Create a WAPT agent
EDIT: I'm a bit absentminded at the moment, the flu is really getting to me. That's precisely why you're creating a custom installer, and that's where you're having problems.
When you installed the console, did you change the default WAPT installation directory?
EDIT: I'm a bit absentminded at the moment, the flu is really getting to me. That's precisely why you're creating a custom installer, and that's where you're having problems.
When you installed the console, did you change the default WAPT installation directory?
From what I've seen, the installation directory for generating a custom installer via the console must be the default one. I've noticed that this also prevents certificate generation via the console.
However, private and public certificates can still be generated using commands. I haven't had the chance to test whether creating a custom installer using Inno-setup causes an error.
It seems this problem stems from a lack of updates to some .py file (I think it was common.py).
However, private and public certificates can still be generated using commands. I haven't had the chance to test whether creating a custom installer using Inno-setup causes an error.
It seems this problem stems from a lack of updates to some .py file (I think it was common.py).
Hi,
So in the end, I completely uninstalled everything, reinstalled using the default settings, and when I click "create installer," here's the result in the image
Thank you for your help.
So in the end, I completely uninstalled everything, reinstalled using the default settings, and when I click "create installer," here's the result in the image
- Capture2.JPG (61.48 KB) Viewed 9735 times
- Capture.JPG (66.48 KB) Viewed 9735 times
- Capture1.JPG (65.71 KB) Viewed 9735 times
