Tranquil IT Forum

Hello,

since the last update, I can no longer connect to the console. Authentication fails even though the login and password are correct.
In the local WAPT configuration, I get an error message regarding server access
: Repository access error: 400 Client Error Server access
error: 400 Client Error.

It's a Debian server.
WAPT Server version: 2.6.0.17226
WAPT Agent version: 2.4.0.14143
WAPT Setup version: 2.6.0.17226
WAPT Deploy version: 2.6.0.17226

Thank you for your help.

Hello,
Was this the documentation followed for this upgrade?
https://www.wapt.fr/fr/doc/wapt-server- ... 2-5-to-2-6
Have a good day,
Bertrand

Yes, I followed that procedure!
Then this one: Updated WAPT from 2.6 to the latest 2.6.
But it didn't change anything.

What is the content of the file /opt/wapt/conf/waptserver.ini?

Here it is:

[options]
waptwua_folder = /var/www/waptwua
server_uuid = db858a52-e1a0-11e8-b004-000c29ee5ea8
wapt_password = $pbkdf2-sha256$secret
allow_unauthenticated_connect = False
allow_unauthenticated_registration = True
secret_key = secret
clients_signing_key = /opt/wapt/conf/ca-WAPT.dec49.pem
clients_signing_certificate = /opt/wapt/conf/ca-WAPT.dec49.crt
wapt_huey_db = /opt/wapt/db/waptservertasks.sqlite
login_on_wads = False
list_subnet_skip_login_wads =
wads_enable = False
token_secret_key = secret
clients_signing_crl = /var/www/ssl/ca-WAPT.dec49.crl
clients_signing_crl_url = http://WAPT.dec49/wapt/ssl/ca-WAPT.dec49.crl
ssl_additional_crls = /var/www/ssl
waptwua_enable = False

Hello,
we confirmed that it worked fine when downloading console version 2.6. The error appeared with console version 2.4.
Best regards,
Bertrand