Tranquil IT Forum

Hello,
We are currently testing the WAPT solution and have a question regarding changing the WAPT server port.
We deployed a WAPT server with the default ports, but after deployment (and adding several workstations), we need to change the WAPT server ports because it will be used by another tool.
Our
question is, how do we re-register all the workstations already present on our console after changing the WAPT server port?
Currently, all the workstations are showing as DISCONNECT on our console.
Thank you for your help.
Sincerely,

I think the simplest solution is to update the client configuration on each workstation so that it points to the server's new port. Otherwise, they remain disconnected because they're trying to connect to the old port. If you have a lot of workstations, this can be done via a script or a Group Policy Object (GPO) deployment to automate the change.

jerome-cis wrote: ↑Jan 20, 2026 - 07:55 but after deployment (and the addition of several workstations), we need to change the WAPT server ports, because it will need to be used by another tool.

Actually, having several applications coexist on the same port is often better.

You just need to perform a TLS transfer based on SNI:

https://www.wapt.fr/fr/doc/wapt-faq-ser ... erse-proxy

Port 443 is the one that's open by default when the Windows firewall is in public mode, and it's often THE open port

The most common solution suggested is to look in that direction