[RESOLVED] Error messages on the WAPT server when more than 500 clients are connected
Published: May 12, 2026 - 10:15
Hello,
We have a WAPT Enterprise 2.6.0.17177 server, installed on a Windows Server 2022 (21H2).
When a number of clients are connected simultaneously, we get errors when using the console, as well as on client workstations when performing actions with the wapt-get command.
The types of error messages we are encountering are:
• Unable to register to waptserver Https://XXX.XXX.XXX.XXX not available (this occurs about half the time when we run wapt-get register)
• Login error: http client error: THttpClientSocket.DoTlsAfter: TLS failed [EOpen SslNetTls EOpen SslNetTls.AfterConnection connect: Open SSL 30400010 error 5 [SSL_ERROR_SYSCALL (10053 ERROR_WSAECONNABORTED)]] (This occurs when attempting to connect to the console and refreshing the list of available packages)
• The server is accessible but not responding correctly. (This occurs on certain console tabs)
These problems appeared suddenly.
Currently, we have an average of over 500 clients connected simultaneously, and approximately 3039 registered. As we are in the deployment phase, these numbers will increase further in the coming months.
Furthermore, as soon as the number of connected clients decreases at the end of the day, the server and console function perfectly again. Moreover, during the "bug" period, a number of clients correctly receive packets and update properly.
Knowing the limitations of Nginx on Windows servers, are these types of error messages and problems directly related to Nginx itself? Especially since it doesn't use many CPU resources under load. Or is there another underlying cause for these problems?
I suspect that Nginx on Windows is showing its limitations, but I haven't found any similar cases on the forum or Discord. I prefer to be certain by asking you this question.
Thank you in advance for your answers.
We have a WAPT Enterprise 2.6.0.17177 server, installed on a Windows Server 2022 (21H2).
When a number of clients are connected simultaneously, we get errors when using the console, as well as on client workstations when performing actions with the wapt-get command.
The types of error messages we are encountering are:
• Unable to register to waptserver Https://XXX.XXX.XXX.XXX not available (this occurs about half the time when we run wapt-get register)
• Login error: http client error: THttpClientSocket.DoTlsAfter: TLS failed [EOpen SslNetTls EOpen SslNetTls.AfterConnection connect: Open SSL 30400010 error 5 [SSL_ERROR_SYSCALL (10053 ERROR_WSAECONNABORTED)]] (This occurs when attempting to connect to the console and refreshing the list of available packages)
• The server is accessible but not responding correctly. (This occurs on certain console tabs)
These problems appeared suddenly.
Currently, we have an average of over 500 clients connected simultaneously, and approximately 3039 registered. As we are in the deployment phase, these numbers will increase further in the coming months.
Furthermore, as soon as the number of connected clients decreases at the end of the day, the server and console function perfectly again. Moreover, during the "bug" period, a number of clients correctly receive packets and update properly.
Knowing the limitations of Nginx on Windows servers, are these types of error messages and problems directly related to Nginx itself? Especially since it doesn't use many CPU resources under load. Or is there another underlying cause for these problems?
I suspect that Nginx on Windows is showing its limitations, but I haven't found any similar cases on the forum or Discord. I prefer to be certain by asking you this question.
Thank you in advance for your answers.