Version upgrade from 2.4 to 2.5.5.15640: Unable to connect to the console after running the postconf.sh script

Questions about WAPT Server / Requests and help related to the WAPT server
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
Answer
cvz
Messages: 2
Registration: May 5, 2023 - 10:07

July 3, 2024 - 10:53

Hello everyone,

I upgraded from version 2.4 to 2.5.5.15640 on an Ubuntu server.
After running the postconf.sh script, I can no longer connect to the console.

The new console version was successfully deployed, and what's surprising is that it keeps asking for the login/password.

In the logs, I have an authentication error:
[waptauth] WARNING Failed auth for admin from 192.168.xx path /api/v3/login.
The admin password hasn't been changed, and even after changing it (by rerunning the script), it's still being requested and the console is unusable.

When an incorrect password is entered, the console correctly indicates that the password is incorrect, so it seems to be a session problem.

I checked the firewall settings, no packets were blocked, and I don't have a proxy between the console and the server.

Since I had taken a snapshot, I performed a rollback, and the problem does indeed appear when running the postconf.sh script. But since running the script seems necessary to retrieve the up machines in the console, I'm a bit lost.

Do you have any ideas?
Thank you in advance.
Best regards,
Dami
Answer