[SOLVED] Wapt 1.8 update: Unable to open the console

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
Locked
agatoi
Messages: 23
Registration: Apr 05, 2017 - 12:03

March 4, 2020 - 3:15 PM

Good morning,

I just updated the server (debian 10) from 1.7 to 1.8.

I also updated the administration console (on Windows 10). But now I can't open it; the console is stuck on the password screen.

On the server, when I run the stop and then start commands (waptserver service stop/start),
I have this in /var/log/daemon.log (/var/log/waptserver.log remains empty):

Code: Select all

Mar  4 15:08:05 srvwapt systemd[1]: Stopping WAPT Server startup script...
Mar  4 15:08:05 srvwapt systemd[1]: waptserver.service: Main process exited, code=killed, status=15/TERM
Mar  4 15:08:05 srvwapt systemd[1]: waptserver.service: Succeeded.
Mar  4 15:08:05 srvwapt systemd[1]: Stopped WAPT Server startup script.
Mar  4 15:08:10 srvwapt systemd[1]: Started WAPT Server startup script.
Mar  4 15:08:14 srvwapt python[3371]: 2020-03-04 15:08:14,103 [waptws         ] WARNING Invalid session None
In short, I need some help.

Thanks in advance
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

March 5, 2020 - 09:17

You can launch the postconf session with password reset:

https://www.wapt.fr/fr/doc/wapt-common- ... n-password
agatoi
Messages: 23
Registration: Apr 05, 2017 - 12:03

March 25, 2020 - 3:56 PM

Yes, it's all good. With the lockdown, I was able to dedicate time to it.

One drawback (very minor, mind you): I had to change my password.
The old one was less than 10 characters long.

Thanks for the help.
Locked