Hello,
I'm using a Debian 12 Linux VM with WAPT 2.4 installed. I can use the WAPT console on Windows 10, but not on Windows Server 2019. Is this a known issue?
Sincerely,
Joel Marchand
Console on Windows Server 2019
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 :
Hello,
no known problems.
Could you provide more information about what isn't working?
Simon
no known problems.
Could you provide more information about what isn't working?
Simon
Hello,
During the installation/registration of waptsetup, I see the following in the WAPT server logs
: root@wapt:/var/log# cat waptserver.log
Oct 8 13:37:01 wapt waptserver[812]: 2023-10-08 13:37:01,428 [waptserver ] WARNING Unauthenticated registration for fsecure2
root@wapt:/var/log#
Then, when I launch the console from W2019, it tells me:
The following servers are not responding: https://wapt.ijm.fr
I have no trace of the firewall between the console and the server.
A tcpdump on the server clearly shows that it receives the console connection and responds:
13:47:26.714529 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 1:276, ack 1, win 32768, length 275
13:47:26.714583 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [.], ack 276, win 501, length 0
13:47:26.715760 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [P.], seq 1:4097, ack 276, win 501, length 4096
13:47:26.719371 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 4097, win 32768, length 0
13:47:26.720890 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [P.], seq 4097:5506, ack 276, win 501, length 1409
13:47:26.723331 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 5506, win 32063, length 0
13:47:26.725067 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 276:283, ack 5506, win 32063, length 7
13:47:26.725399 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [F.], seq 5506, ack 283, win 501, length 0
13:47:26.725989 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 5507, win 32063, length 0
13:47:26.726774 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [R.], seq 283, ack 5507, win 0, length 0
13:47:29.046438 IP fw455.ijm.univ-paris-diderot.priv.51613 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 1638281247:1638281283, ack 2087077311, win 8207, length 36
13:47:29.047881 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51613: Flags [P.], seq 1:33, ack 36, win 501, length 32
13:47:29.060767 IP fw455.ijm.univ-paris-diderot.priv.51613 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 33, win 8207, length 0
Kind regards,
Joel Marchand
During the installation/registration of waptsetup, I see the following in the WAPT server logs
: root@wapt:/var/log# cat waptserver.log
Oct 8 13:37:01 wapt waptserver[812]: 2023-10-08 13:37:01,428 [waptserver ] WARNING Unauthenticated registration for fsecure2
root@wapt:/var/log#
Then, when I launch the console from W2019, it tells me:
The following servers are not responding: https://wapt.ijm.fr
I have no trace of the firewall between the console and the server.
A tcpdump on the server clearly shows that it receives the console connection and responds:
13:47:26.714529 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 1:276, ack 1, win 32768, length 275
13:47:26.714583 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [.], ack 276, win 501, length 0
13:47:26.715760 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [P.], seq 1:4097, ack 276, win 501, length 4096
13:47:26.719371 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 4097, win 32768, length 0
13:47:26.720890 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [P.], seq 4097:5506, ack 276, win 501, length 1409
13:47:26.723331 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 5506, win 32063, length 0
13:47:26.725067 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 276:283, ack 5506, win 32063, length 7
13:47:26.725399 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51654: Flags [F.], seq 5506, ack 283, win 501, length 0
13:47:26.725989 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 5507, win 32063, length 0
13:47:26.726774 IP fw455.ijm.univ-paris-diderot.priv.51654 > wapt.ijm.univ-paris-diderot.priv.https: Flags [R.], seq 283, ack 5507, win 0, length 0
13:47:29.046438 IP fw455.ijm.univ-paris-diderot.priv.51613 > wapt.ijm.univ-paris-diderot.priv.https: Flags [P.], seq 1638281247:1638281283, ack 2087077311, win 8207, length 36
13:47:29.047881 IP wapt.ijm.univ-paris-diderot.priv.https > fw455.ijm.univ-paris-diderot.priv.51613: Flags [P.], seq 1:33, ack 36, win 501, length 32
13:47:29.060767 IP fw455.ijm.univ-paris-diderot.priv.51613 > wapt.ijm.univ-paris-diderot.priv.https: Flags [.], ack 33, win 8207, length 0
Kind regards,
Joel Marchand
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
What does the command return? on the client machine?
Code: Select all
wapt-get register- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Can you start in debug mode to see?
Code: Select all
"c:\Program Files (x86)\wapt\waptconsole.exe" -ldebugThank you!
1st attachment: what's happening on Windows Server 2019.
2nd attachment: what's happening on Windows 10.
Best regards,
Joel
1st attachment: what's happening on Windows Server 2019.
2nd attachment: what's happening on Windows 10.
Best regards,
Joel
- Attachments
-
- Screenshot from 2023-10-09 13-49-39.png (71.99 KB) Viewed 5895 times
-
- Screenshot from 2023-10-09 13-48-10.png (70.66 KB) Viewed 5895 times
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
According to the message, it's the HTTPS certificate verification that isn't working. How do I configure HTTPS verification in the console?
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
When you open waptconsole.exe,
you should normally see a small wrench icon next to the server name (before clicking OK).
You will then see a "Verify HTTPS server certificate" button and below it, "Path to certificate bundle".
you should normally see a small wrench icon next to the server name (before clicking OK).
You will then see a "Verify HTTPS server certificate" button and below it, "Path to certificate bundle".
