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.
[RESOLVED] Authentication error since update
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
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
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
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
-
llecaplain
- Messages: 8
- Registration: March 7, 2016 - 12:34
Yes, I followed that procedure!
Then this one: Updated WAPT from 2.6 to the latest 2.6.
But it didn't change anything.
Then this one: Updated WAPT from 2.6 to the latest 2.6.
But it didn't change anything.
-
llecaplain
- Messages: 8
- Registration: March 7, 2016 - 12:34
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
[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
