[SOLVED] Error after Debian Trixie installation

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
Emmanuel64
Messages: 46
Registration: February 23, 2024 - 09:37

August 12, 2025 - 2:37 PM

Hello

, I'm posting more for information than for an immediate solution!

After upgrading to Debian 13, I'm encountering errors in the nginx configuration, specifically with the "auth_gss*" directives:
unknown directive auth_gss,
unknown directive "auth_gss_allow_basic_fallback",
auth_gss_keytab,
unknown directive auth_gss_format_full.

Commenting them out works, but that's not the intended solution. ;-)
WAPT Enterprise
Version 2.6.1.17576
User avatar
sfonteneau
WAPT Expert
Messages: 2318
Registered: July 10, 2014 - 11:52 PM
Contact :

August 12, 2025 - 3:42 PM

Hello,

actually, debian13 added the "nginx-mod-http-auth-spnego" package to its repository, which we previously provided.

The problem is that this package is an older version than the one we were offering.

Therefore, the simplest solution is indeed to temporarily disable Kerberos on WAPT (before migration) via Postconf.

- Uninstall the "nginx-mod-http-auth-spnego" package.

- Perform the migration to Trixie.

- Reinstall the nginx-mod-http-auth-spnego package and restart Postconf to re-enable Kerberos.
Emmanuel64
Messages: 46
Registration: February 23, 2024 - 09:37

August 12, 2025 - 4:04 PM

Thanks for the feedback.

Apparently, the nginx-mod-http-auth-spnegon package is not available.

NB: My mistake, the package is libnginx-mod-http-auth-spnego :P
WAPT Enterprise
Version 2.6.1.17576
Locked