Hello,
We are currently testing the WAPT solution and have a question regarding changing the WAPT server port.
Our
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.
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,
Change of WAPT server port - and reconnection of all workstations.
Forum Rules
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
Community Forum Rules
* English support on www.reddit.com/r/wapt
* French community support is available on this forum
* Please prefix the topic title with [RESOLVED] if it is resolved.
* Please do not edit a topic that is tagged [RESOLVED]. Open a new topic referencing the old one.
* Specify the installed WAPT version, full version, and build number (2.2.1.11957 / 2.2.2.12337 / etc.) as well as the Enterprise/Discovery edition.
* Versions 1.8.2 and earlier are no longer supported. The only questions accepted regarding version 1.8.2 are related to upgrading to a supported version (2.1, 2.2, etc.).
* Specify the server OS (Linux/Windows) and version (Debian Buster/Bullseye - CentOS 7 - Windows Server 2012/2016/2019).
* Specify the OS of the administration/package creation machine and the machine with the problematic agent, if applicable (Windows 7/10/11/Debian 11/etc.).
* Avoid asking multiple questions when opening a topic, otherwise it may be ignored. If there are multiple topics, open separate topics, preferably one after the other and not all at the same time (i.e., do not spam the forum).
* Include code snippets, screenshots, and other images directly in the post. Links to Pastebin, Bitly, and other third-party sites will be systematically removed.
* As with any community forum, support is provided voluntarily by members. If you require commercial support, you can contact Tranquil IT's sales department at 02.40.97.57.55
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.
-
sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Actually, having several applications coexist on the same port is often better.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.
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
