Version upgrade from 2.4 to 2.5.5.15640: Unable to connect to the console after running the postconf.sh script
Published: July 3, 2024 - 10:53 AM
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
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