Tranquil IT Forum

Hi!

After several tests, I'm left with a wapt1.5 server that's not very usable... here's my problem: I'm stuck... the Running status no longer changes and each Check Update creates an error (irreversible)

Thank you all (good webcasting too)

When there's an error, there are two possibilities:
- The WAPT client can't validate the signature of the request sent by the console: is the certificate deployed on the client the same as the one used to sign in the console?
- The WAPT client has disconnected from the server (and possibly reconnected with a different WebSocket session ID) since the grid was displayed.

You can get more information by checking "View debug information" in the "Display / Display Preferences" menu.

To clarify how it works:
- When the action is initiated on the client, the WAPT server sets the status to RUNNING while waiting for a response from the client
. - When the response comes back via the WebSocket channel, the status is updated in the database.

Okay,
I'm in debug mode and yes, it's definitely a key problem: My question is... should I look at it from the client side or the server side?

THANKS.

In both cases...
It's important to verify that the certificate on the client is correct. <répertoire de wapt>\ssl is the same as the one you use to sign packets and actions in the console (defined by the personal_certificate_path in %LOCALAPPDATA%\waptconsole\waptconsole.ini)

Yes, it was a key error (thanks for the advanced mode tip).
I had to recreate my key and re-sign my packages because in the meantime my server changed domain and name... plus migrated from wapt 1.3 to 1.5...
thanks