Hello,
WAPT Server version: 2.5.5.15556
WAPT Agent version: 2.3.0.13516
WAPT Setup version: 2.5.5.15556
WAPT Deploy version: 2.5.5.15556
Database status: OK
Following an update from version 2.3 to version 2.5, I can no longer connect to the WAPT console.
It was updated via the URL, as specified in the 2.5 update documentation: https://www.wapt.fr/fr/doc/wapt-server-upgrade.html
When I connect via the web interface, with the same account, it works, but when I connect via the console, it doesn't open and perpetually displays the authentication window.
On the server side, the debug logs for authentication show the following:
IMAGE REMOVED (see forum rules).
It clearly ends with "Failed auth for admin from XXXX path /api/v3/login", however, I see no explanation.
All tests were also performed using wapt version 2.5.5.15549.
The WAPT version is enterprise, and the tests were carried out on Debian 11 and 12, each time using the tis package for the version in question.
[RESOLVED] Unable to connect to the console after update 2.5
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
Hello,
If the configuration is correct at the console level,
then I suggest you repeat the postconf procedure and reset your password.
https://www.wapt.fr/fr/doc/wapt-postcon ... t-postconf
Best regards
If the configuration is correct at the console level,
then I suggest you repeat the postconf procedure and reset your password.
https://www.wapt.fr/fr/doc/wapt-postcon ... t-postconf
Best regards
Hello,
Finally, after investigation, the problem stemmed from the Reverse Proxy. The documentation specified that the agents no longer supported TLS Reverse Proxy and that simple SNI streams were required; however, this impacted not only the agents but also the console. :/
This has now been fixed, but since the reverse proxy is shared, a different port than 443 had to be used for the stream.
This also required changing the port in the waptdeploy GPO and adding "setupargs" to it so that the agents point to the correct ports.
In short, quite a few changes for version 2.5, but everything seems to be working.
Finally, after investigation, the problem stemmed from the Reverse Proxy. The documentation specified that the agents no longer supported TLS Reverse Proxy and that simple SNI streams were required; however, this impacted not only the agents but also the console. :/
This has now been fixed, but since the reverse proxy is shared, a different port than 443 had to be used for the stream.
This also required changing the port in the waptdeploy GPO and adding "setupargs" to it so that the agents point to the correct ports.
In short, quite a few changes for version 2.5, but everything seems to be working.
Hello,
That's great then.
Indeed, version 2.5 has placed considerable emphasis on security, and the reverse proxy requires modifications...
I commend your thorough analysis and its complete resolution.
Thank you for this feedback
Best regards
That's great then.
Indeed, version 2.5 has placed considerable emphasis on security, and the reverse proxy requires modifications...
I commend your thorough analysis and its complete resolution.
Thank you for this feedback
Best regards
