Tranquil IT Forum

Hello everyone,

We've been using WAPT to manage our infrastructure for a while now, and we initially opted for a Windows Server 2022 installation, aware of the limit on the number of machines (around 200 according to the documentation).

Our infrastructure has grown a bit more than expected, and we'll soon reach that limit.

At the end of last year, to get some experience, I created a WAPT server running Ubuntu, which has been serving as a secondary repository until now.

Since the beginning of this week, I've decided to make this secondary repository the primary server.
So, I updated both servers to the latest version of WAPT (2.6.1.17765).

Since my Ubuntu server was my secondary server, the packages were already on it, so no problem there.

I was able to connect my console to this new server without any issues, and my admin certificates are OK. However,
when I go to the private repository section, I don't see my packages.

Looking at the documentation, I realize I forgot to run `wapt-scanpackages` to resign my packages... and that's where things get complicated.

When I run this command, I get an SSL error:
Warning Unable to download CRL from __http://pki.domain.local/CertEnroll/Crl/autorite_Racine_Domain.crl__: SSLVerifyException("CRL Issuer CA certificate {'commonName': Autorite Racine Domain'} can not be found in supplied bundle").

I retrieved the bundle from my old server and put it on the new one, but the problem remains the same.

I'm a bit stuck; do you have any ideas?

Hello,

We also manage a WAPT server running on Windows Server 2022 and support just over 1,000 workstations.

I just learned from your support ticket that there's a limit of 200 workstations maximum. I wasn't aware of this restriction during our initial setup.

I'd like to know if it's necessary to plan a migration to Linux, or what the risks are of continuing to use our current Windows version.

Thank you in advance for your response.

Hello Christophe,

This information is described here: https://www.wapt.fr/fr/doc/wapt-server- ... ndows.html
The first bullet point in the "Read beforehand" section:
Installing WAPT on a Linux server is the recommended method, unless you are testing WAPT and are not familiar with Linux. Due to a technical limitation of the Nginx server under Windows, the maximum number of agents supported by WAPTServer on Windows is 200.

The limitation seems to stem from Nginx on Windows, but your message reassures me if your server handles your 1,000 workstations very well.

I am not familiar with Tranquil.IT's official recommendations on this subject, and I don't know if this limitation is still in effect.

If I migrate, it's primarily to have user authentication via Active Directory.

Hello everyone

, My problem is solved. I had a path issue with my WAPT packages after migrating from Windows to Linux.
Once this was fixed, I was able to re-sign my packages on my new server.

@christophe: Your question regarding the limit on the number of workstations on a Windows server is quite interesting; it might be a good idea to start a new thread to get a more "official" answer.

Hi Julien,

thanks for the update , glad everything is back to normal!

Denis