Hello,
I'm having a problem (actually two...) when creating the agent on a fresh WAPT 1.5 installation under Windows.
First, I don't understand the purpose of the "Verify HTTPS server certificate" checkbox in the agent creation interface.
In any case, I had to uncheck it; otherwise, the agent wouldn't be created, displaying the error message shown in the attached image (Attachment 1).
Second, and more annoyingly, if I uncheck this box, the agent creation process does proceed and seems to complete normally (see Attachment 2). However, I can't access the agent from the web interface (Attachment 3).
For your information, I created the agent directly from the server.
Any ideas?
Thanks in advance.
[SOLVED] Problem creating the agent
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
Good morning,
If your server's certificate (srvwaptav.lyceestjo.fr) is not valid (self-generated and not issued by a recognized certification authority, e.g., Gandi), then it is normal that it does not work.
This procedure is documented: https://www.wapt.fr/fr/doc/Installation ... icate.html
When sending the agent, this certificate is checked and this also prevents it from being sent to the server; fix this issue and it will be functional.
Alexander
The checkbox allows you to verify the HTTPS SSL/TLS certificate of your WAPT server during exchanges with the agent.First, I don't understand the purpose of the "verify HTTPS server certificate" checkbox in the agent creation interface.
In any case, I had to uncheck it; otherwise, the agent wouldn't be created, resulting in the error message shown in the attached image (AP1).
If your server's certificate (srvwaptav.lyceestjo.fr) is not valid (self-generated and not issued by a recognized certification authority, e.g., Gandi), then it is normal that it does not work.
This procedure is documented: https://www.wapt.fr/fr/doc/Installation ... icate.html
When sending the agent, this certificate is checked and this also prevents it from being sent to the server; fix this issue and it will be functional.
Alexander
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Just to be sure, I tried again, and it works for me.
The documentation says to modify the Windows firewall on the WAPT server. But perhaps your antivirus also acts as a firewall and is blocking port 8443?
On the server, the interface responds at: https://127.0.0.1:8443 ??
The documentation says to modify the Windows firewall on the WAPT server. But perhaps your antivirus also acts as a firewall and is blocking port 8443?
On the server, the interface responds at: https://127.0.0.1:8443 ??
Yes, that works. I can access the server's homepage on the LAN.
However, I just saw in the documentation that the private key and certificate should be created from another machine.
But I did it directly on the server by installing waptsetup...
Could that be the reason for my problem?
Thanks.
However, I just saw in the documentation that the private key and certificate should be created from another machine.
But I did it directly on the server by installing waptsetup...
Could that be the reason for my problem?
Thanks.
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
This is indeed not recommended for safety reasons.PPE wrote: ↑March 20, 2018 - 8:19 AM Yes, that answers your question. I can access the server's homepage on the LAN.
However, I just saw in the documentation that the private key and certificate creation should be done from another machine.
But I did it directly on the server by installing waptsetup...
Could that be the reason for my problem?
Thanks.
But that doesn't explain your problem
Okay... Well, I'm stuck. I tested the link to waptdeploy and it works. (see attached image)
In which folder should waptsetup be saved so I can check if it's there?
Thanks.
In which folder should waptsetup be saved so I can check if it's there?
Thanks.
- Attachments
-
- Screenshot 2018-03-20 at 09:54:14.png (19.89 KB) Viewed 7145 times
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning,
As Simon indicated:
The presence of this installer is not essential for the proper functioning of the WAPT server; this installer will only be used when installing your console on the administrator's workstation.
Alexander
As Simon indicated:
Code: Select all
Pour la suite, télécharger manuellement WAPTSetup depuis : https://wapt.tranquil.it/wapt/releases/latest/waptsetup.exeAlexander
Hello Alexandre,
As I mentioned earlier, I've already downloaded this "generic" waptsetup. My problem concerns the "custom" waptserver-tis.exe file which, despite the agent generation running correctly, isn't available via the server link.
So I'm trying to verify that the waptserver-tis.exe file is saved in the correct location on the server... but I don't know where to look.
I hope that's clear...
As I mentioned earlier, I've already downloaded this "generic" waptsetup. My problem concerns the "custom" waptserver-tis.exe file which, despite the agent generation running correctly, isn't available via the server link.
So I'm trying to verify that the waptserver-tis.exe file is saved in the correct location on the server... but I don't know where to look.
I hope that's clear...
