GUI Port and HTTPS Redirect
Overview
The Energy Logserver web GUI (logserver-gui service) listens on TCP port 5601 by default. To allow users to reach the GUI on the standard HTTPS port, the installer adds a firewalld port-forwarding rule that redirects incoming traffic from port 443 to port 5601 on the same host.
This redirect is created only when firewall-cmd is available on the system. On hosts without firewalld, no automatic redirect is configured, operators must set up their own mechanism (iptables, nginx, HAProxy, or a load balancer in front of the Console).
Changing the GUI port therefore requires updating both the GUI configuration file and the firewalld redirect; updating only the configuration file leaves the redirect pointing at the old port and the GUI appears unreachable on 443.
Default configuration
Item |
Value |
|---|---|
GUI configuration file |
|
Default listen port ( |
|
Default bind address ( |
|
Installer-added redirect |
firewalld forward |
Service unit |
|
To inspect the active firewalld rules:
firewall-cmd --list-ports
firewall-cmd --list-forward-ports
A standard install reports 5601/tcp (along with 5602/tcp and 5603/tcp) in the open ports list and port=443:proto=tcp:toport=5601:toaddr= in the forward-ports list.
Changing the GUI port
The example below changes the GUI port from 5601 to 5701. Replace 5701 with your target port.
1. Update the GUI configuration file
Edit /etc/logserver-gui/logserver-gui.yml and set server.port to the new value:
server.port: 5701
server.host: "0.0.0.0"
server.host only needs to change if you also want to restrict the bind address (for example, to 127.0.0.1 when the GUI is fronted by a reverse proxy on the same host).
2. Update the firewalld redirect
Remove the old port-forward and the old port, then add the new ones:
firewall-cmd --permanent --zone=public --remove-forward-port=port=443:proto=tcp:toport=5601
firewall-cmd --permanent --zone=public --remove-port=5601/tcp
firewall-cmd --permanent --zone=public --add-port=5701/tcp
firewall-cmd --permanent --zone=public --add-forward-port=port=443:proto=tcp:toport=5701
firewall-cmd --reload
The masquerade setting on the public zone must remain enabled, the firewalld forward-port rule depends on it. The installer enables it by default; do not remove it.
3. Restart the GUI service
systemctl restart logserver-gui
4. Verify
ss -ltnp | grep 5701
curl -kI https://127.0.0.1:5701/
curl -kI https://<server-fqdn>/
The first command confirms the GUI is listening on the new port. The second confirms the GUI responds directly. The third confirms the 443 redirect now lands on the new port.
Hosts without firewalld
If firewall-cmd was not present at install time, the installer skipped both the open-port rules and the 443→5601 forward. In that case:
Reaching the GUI on 443 requires an external mechanism that you control (iptables, nginx, HAProxy, an upstream load balancer, or a cloud-provider rule). The installer does not configure any of these.
Changing the GUI port only requires steps 1, 3, and 4 above. The redirect update belongs to whichever tool you used to publish the GUI on 443.
For a documented NGINX reverse-proxy setup (used with OAuth2 / 2FA), see Authentication and Directory Integration. When you put your own proxy on port 443, remove the installer’s 443 → 5601 forward first, otherwise the PREROUTING redirect intercepts external traffic before your proxy sees it, and the proxy never runs even though loopback tests succeed.
Caveats
Integrations with hard-coded GUI URLs. Some bundled components (Alert, Reports, the Intelligence module, and parts of the installer’s own post-install steps) call the GUI on
https://127.0.0.1:5601. After changingserver.port, search component configuration files for5601and update any references you find. Restart each affected service.Re-running the installer. If you re-run
install.shafter changing the port, the installer may re-add the original443 → 5601forward-port rule. Re-apply your firewalld changes after any reinstall or upgrade that re-executes the installer’s firewalld block.Cluster deployments. Apply the change on every Console node. The port must match across nodes that share a load balancer or DNS name.
TLS termination. When TLS is terminated upstream (by NGINX or a load balancer), the GUI can be configured to listen over HTTP, disable
server.ssl.enabledinlogserver-gui.ymland bindserver.hostto127.0.0.1so the GUI is not reachable directly from the network.