Hello,

Without any intervention on my part, the status has returned to green since last Thursday!
The mysteries of computers have struck again

Thank you and have a good day,
Christophe

Denis,

we're on Debian 13 and SELinux is not enabled.

Hi Denis,

So indeed, we hadn't run the postconf, but that doesn't fix the problem.
Regarding the sync.json file, it's present with a consistent date and time (this morning), and when I select "update index", it says "updating sync.json..."

Hello,

Following the migration of our main server to Linux (previously Windows), our secondary repositories, which are still on Windows, remain in a "TO UPDATE" synchronization status. Aside from this, everything seems to be working.
Status.png

Our WAPT version is 2.6.1...

Does anyone have any ideas?

Should I uninstall and then reinstall the NGINX Remote Repository package?

Or could it be a path issue following the switch from Windows to Linux? In that case, could you tell me how to change the path and what to put there?

Here's my...

All things considered, we do have a small problem.

Since the migration, our secondary repositories on Windows 11 are not synchronizing with the Linux server.

Do you have any idea what the issue might be?
Thank you.

It's all good, we've fixed the problem.
Our migration went smoothly.

Thank you and have a good day,
Christophe

Hi Bastien,

I was also experiencing this type of error on our Windows server, which handles just over 1,000 clients (THttpClientSocket.DoTlsAfter and a frozen console).
With over 3,000, it must be even worse.

I think migrating to the Linux version is necessary.
We have...

Hello,

Following the migration, my WAPT client no longer installs automatically because it requires a password to register the machine on the server. This password is for the new Linux server. We had to change it because, under Linux, a 10-character password...

Great, thanks. I'll take a look.