Hello,
I have a WAPT server, version 2.5, installed on Debian 11.
To set up external access to the server from workstations via a shared network, I need to change the HTTP and HTTPS ports of my WAPT server.
I saw in the 2.5 documentation that this is possible on Windows by modifying the waptserver.ini file,
but I haven't found how to do it on Linux. I tried modifying configuration files, but without success.
Could you please tell me how to proceed?
Changes to HTTP/HTTPS ports on WAPT server v2.5 Debian 11
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
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
Good morning
In :
/opt/wapt/conf/waptserver.ini
Add :
And relaunch a post-conference
This should work
In :
/opt/wapt/conf/waptserver.ini
Add :
Code: Select all
[options]
nginx_https = 4443
nginx_http = 480
This should work
Thank you for your quick reply.
Despite editing waptserver.ini and running postconf, I still cannot access my server (see attached image), whereas if I reset the ports to default (comment out the two added lines and run postconf) it works.
Despite editing waptserver.ini and running postconf, I still cannot access my server (see attached image), whereas if I reset the ports to default (comment out the two added lines and run postconf) it works.
- Attachments
-
- wapt-erreur.png (10.53 KB) Viewed 4652 times
- sfonteneau
- WAPT Expert
- Messages: 2318
- Registered: July 10, 2014 - 11:52 PM
- Contact :
What does this give?
Has nginx been restarted?
You wouldn't happen to have an additional firewall blocking access to the new port, would you?
try on the server:
Code: Select all
netstat -pnat |grep nginx |grep "0.0.0.0"Has nginx been restarted?
You wouldn't happen to have an additional firewall blocking access to the new port, would you?
try on the server:
Code: Select all
curl https://127.0.0.1:8443 --insecure