Tranquil IT Forum

Good morning,

I had to migrate my WAPT server based on the Oracle cloud. At first glance, everything went well, I backed up the server (which was at 2.6.1.17834) and I performed a restore (to a WAPT server which was therefore mounted at 2.6.1.17861).
Following the last postconf (and the download/install of the generated waptsetup.exe), I can authenticate at the console level (with all existing accounts), I have successfully retrieved the inventory of my machines, all the packages from my repository as well as the SQL queries.
I can edit the packages in my repository and download new ones from the Tranquil IT store, and I haven't encountered any problems interacting with the machines either.

However, I am encountering two problems:

1. Although I can authenticate via the console with all existing users (I only have one user in addition to "admin"), I cannot authenticate at the WAPT server web interface level. It repeatedly prompts me for a login/password request regardless of the user (even with "admin") as if I were entering incorrect credentials (I have copied and pasted them several times to be sure).
I tried changing my user password via the console and restarting the services on the server, but that didn't change anything.

2. Following the postconf, I was able to regenerate a wapt agent via the console for the Windows machines (no problem and the agent updated correctly on the machines), however, it was impossible to "download and send the WAPT agent installers to the server" (for Linux and Mac) via the console.
I tried once without success, then I ran the script "get_linux_and_macos_agent.sh" and tried again from the console, still without success.
I'm getting this error message:

Basically, that's it... if anyone has any ideas... I'll continue to look into it on my end.
Thank you in advance.

Regards,
Bastien

Hello,
do you have Kerberos authentication enabled on the server side?
Are you using Chrome/Chromium for the web interface?
If so, could you try with Firefox?

There's a difference in behavior when encountering a 401 status between the two browsers.

If you have some time, I can look into this with you; please call us at

Hubert Touvet,
Tranquil IT.

We've fixed both issues:
A release is planned soon (before the end of the week)

https://wapt.tranquil.it/wapt/nightly/w ... -c88b2627/

Version 2.6.1.17870-d3b9238d is released with the 2 fixes.

Hello,

Sorry, I didn't have access to the server. The license for this server was purchased through Comitari (so I don't really have "professional" support).
Thanks in advance for the community support offered via the forum. And thanks again for the quick response!

To answer (a bit late, I know), yes, I am indeed using a Chromium-based browser (I did see in the Nginx logs that I was getting 401 errors, but without any further details...). I installed Firefox and, unsurprisingly, there are no authentication issues with the server's web interface.

I also have Kerberos authentication enabled on the server side (even though I haven't really used it yet)... could this be related to the Linux/Mac agents not being able to be updated?

In any case, thanks again. I'll do the update fairly soon and will let you know if necessary.

Best regards,
Bastien

Hello,

Just a quick update: following the update, I was able to update the Linux/Mac agents without any problems.
Using a Chromium web browser, the web interface is accessible with the admin account, but I still get a 401 error with the second user account (the local account on the WAPT server), which works fine, of course, if I use Firefox.

Regards,
Bastien

Hello Bastien,

b.ald wrote: ↑September 2, 2026 - 7:44 PM Just to give a quick update, following the update, I was able to update the Linux/Mac agents without any problems.
With a Chromium web browser, the web interface is accessible with the admin account, but I still get a 401 error with the second user account (local account on the WAPT server), which of course works if I use Firefox.

This was corrected on 2-6-1-17870 [1].

Sorry for the inconvenience

Denis

[1] https://www.wapt.fr/fr/doc/wapt-changel ... 2026-09-01

Good morning,

Sorry for the delayed response.

Yes, I did the upgrade that same evening after seeing Hubert's post.
My bad, indeed, I tried again and I can authenticate (using chrome) with the user present in the "htpasswd".
But I couldn't say why, it only works on the second attempt... the first attempt always fails as you can see in the screenshot (the three 401 lines correspond to the first attempt, and the following one works...) That's just a minor detail. Anyway, thanks again!

Regards,
Bastien