Page 1 of 1

[RESOLVED] Unable to connect to the console after update 2.5

Published: May 2, 2024 - 3:04 PM
by aleduc
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.

Re: Unable to connect to the console after update 2.5

Published: May 3, 2024 - 3:43 PM
by Jarnaud
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

Re: Unable to connect to the console after update 2.5

Published: May 14, 2024 - 10:28
by aleduc
Hello,

The password has been changed via the postconf script, but unfortunately, the problem remains the same :/.

Regards,

Re: Unable to connect to the console after update 2.5

Published: May 15, 2024 - 09:32
by aleduc
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.

Re: Unable to connect to the console after update 2.5

Published: May 16, 2024 - 4:40 PM
by Jarnaud
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