Hello,
I'm experiencing unreachable workstations on the server again.
I launched debug mode to test and got the result below.
I checked the personal certificates in Tools > Preferences. I verified the associated key and everything is OK. I copied this key to Program Files (x86)\wapt\ssl to be sure it's in the .crt file, but it didn't help... If you have any ideas on how to resolve this issue, I would appreciate it.
Best regards
2023-03-10 08:13:15,970 [urllib3.connectionpool WaptTaskManager 7220] DEBUG Starting new HTTPS connection (1): 10.39.12.9:443
2023-03-10 08:13:18,900 [urllib3.connectionpool SocketIOClient 13292] DEBUG Starting new HTTPS connection (1): 10.39.12.9:443
2023-03-10 08:13:18,931 [waptws SocketIOClient 13292] WARNING Exception SSLError(MaxRetryError("HTTPSConnectionPool(host='10.39.12.9', port=443): Max retries exceeded with url: /get_websocket_auth_token (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate (_ssl.c:1131)')))"), waiting 60s before retrying
2023-03-10 08:13:26,008 [waptcore WaptTaskManager 7220] DEBUG DB Start transaction
2023-03-10 08:13:29,513 [waptcore WaptTaskManager 7220] DEBUG Transaction took too much time: 3.504660129547119
[RESOLVED] Issue with the phone being reachable
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: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Jean-Philippe,
what version of WAPT are you using? What is the server OS? What is the client OS?
The machine is unable to validate the server's HTTPS certificate. You need to either correct the certificate issue (is the CA missing locally on the machine?), pin the server certificate to the machine, switch to HTTP without TLS, or ignore the certificate altogether.
Regards,
Denis
what version of WAPT are you using? What is the server OS? What is the client OS?
The machine is unable to validate the server's HTTPS certificate. You need to either correct the certificate issue (is the CA missing locally on the machine?), pin the server certificate to the machine, switch to HTTP without TLS, or ignore the certificate altogether.
Regards,
Denis
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
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello,
since I haven't received a response, I assume the HTTPS certificate issue has been resolved... I'm marking this topic as resolved.
Regards,
Denis
since I haven't received a response, I assume the HTTPS certificate issue has been resolved... I'm marking this topic as resolved.
Regards,
Denis
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
Hello,
no, I'm still in the testing phase.
I don't understand why the workstations have different SHA256 hashes. Some start with 636xxxxxx, others with c5b75xxxxxxxx. Shouldn't the hash be the same for all workstations?
Furthermore, I just noticed that workstations with different hashes were correctly identified by the console interface. So my problem probably isn't related to the certificate.
The client workstation I'm using for the console interface is running Windows 10, and the server is running Windows Server 2019.
WAPT console version 2.3.0.13470.
Regards
no, I'm still in the testing phase.
I don't understand why the workstations have different SHA256 hashes. Some start with 636xxxxxx, others with c5b75xxxxxxxx. Shouldn't the hash be the same for all workstations?
Furthermore, I just noticed that workstations with different hashes were correctly identified by the console interface. So my problem probably isn't related to the certificate.
The client workstation I'm using for the console interface is running Windows 10, and the server is running Windows Server 2019.
WAPT console version 2.3.0.13470.
Regards
-
dcardon
- WAPT Expert
- Messages: 1930
- Registration: June 18, 2014 - 09:58
- Location: Saint Sébastien sur Loire
- Contact :
Hello Jean-Philippe,
the client certificate fingerprint issue is different from the server's HTTPS certificate issue. Please start a new thread. Regarding the fingerprints, please specify where you obtained them. I'm locking this topic.
Regards,
Denis
the client certificate fingerprint issue is different from the server's HTTPS certificate issue. Please start a new thread. Regarding the fingerprints, please specify where you obtained them. I'm locking this topic.
Regards,
Denis
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
