Book Demo!

˂ Return to FAQ

How to change XTAM’s Web GUI Port Number

To avoid a possible conflict on the standard https port of 443, XTAM is installed to use port 6443 for its web GUI (https://server:6443/xtam). If you want to change this port to something other than 6443, like the standard https port 443, then please follow the steps described in this article.

Before changing the port to 443 make sure that there is no other software running on this port on the operating system (such as MS IIS or Apache HTTPD Server) to avoid port conflicts. If something else is already running on this port, then XTAM will fail to start.

For Windows deployments

1

Log on the XTAM host server and open the file $XTAM_HOME/web/conf/server.xml in a text editor.

2

Search for the value 6443. There will be only one occurrence of this value in the file.

3

Change this value from 6443 to 443.

4

Save and close the file.

5

Restart the PamManagement service.

When the service fully restarts, your XTAM server will be listening on port 443 (https://server:443/xtam or simply https://server/xtam)

For Linux deployments installed and run with root account

1

Log on the XTAM host server and open the file $XTAM_HOME/web/conf/server.xml in a text editor.

2

Search for the value 6443. There will be only one occurrence of this value in the file.

3

Change this value from 6443 to 443.

4

Save and close the file.

5

Restart the pammanager service.

For Linux deployments installed and run with a non-root user account

Because XTAM was deployed and running with a non-root account, Linux will not allow XTAM to be bound to low number port such as 443. In this case, there are two options:

First is to follow the documentation of your operating system and disable this behavior so that Linux will allow a non-root user to bind to the port 443. We do not recommend this option for production deployments, but for non-production deployments like test, trial or ‘proof of concept’ environments this may be considered.

Second is to leave XTAM on its default port 6443 and configure a third party load balancer (reversed proxy) to listen on the port 443 and pass through the HTTP traffic to the XTAM server. The below article describes the configuration of Apache HTTPD proxy server to act as a load balancer for two XTAM nodes, but the same concept with a single node will serve a single node deployment. You can also use any other load balancer too such as an F5.

https://www.xtontech.com/blog/load-balancer-configuration-apache-http-server-sticky-sessions/

It’s worth noting again, regardless of which option applies to your deployment, before changing the port to 443 make sure that there is no other software running on this port on the operating system (such as MS IIS or Apache HTTPD Server) to avoid port conflicts. If something else is already running on this port, then XTAM will fail to start.

 
 

Copyright © 2020 Xton Technologies, LLC. All rights reserved.