Why do I get an error after trying to enable the collector communication to port 443 via the portal appliance’s webconsole?
The error reported is: "Impossible to save TCP port 443 allowed configuration" and does not really give an indication as to why this happens.
You may also notice that the nginx service fails to start with the following at the same time.
[nexthink@portal]$ sudo systemctl status nginx ● nginx.service - nginx - high performance web server Loaded: loaded (/usr/lib/systemd/system/nginx.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Wed 2020-06-03 11:03:16 CEST; 3min 28s ago Docs: http://nginx.org/en/docs/ Process: 113678 ExecStop=/bin/kill -s TERM $MAINPID (code=exited, status=0/SUCCESS) Process: 113685 ExecStart=/usr/sbin/nginx -c /etc/nginx/nginx.conf (code=exited, status=1/FAILURE) Main PID: 110271 (code=exited, status=0/SUCCESS) Jun 03 11:03:16 portal systemd: Starting nginx - high performance web server... Jun 03 11:03:16 portal nginx: nginx: [emerg] host not found in upstream "portal.vm" in /var/nexthink/nxnginx/conf.d/services/ws.conf:2 Jun 03 11:03:16 portal systemd: nginx.service: control process exited, code=exited status=1 Jun 03 11:03:16 portal systemd: Failed to start nginx - high performance web server. Jun 03 11:03:16 portal systemd: Unit nginx.service entered failed state. Jun 03 11:03:16 portal systemd: nginx.service failed.
Make sure the appliance can resolve its own hostname either by DNS or add a static entry in /etc/hosts to resolve this issue.
We have also seen a corner case where the IPv6 config was not present on the network interface causing the same error. In that case, permanently enable IPv6 by editing the /etc/sysctl.conf file, add or change the lines below to match and reboot the appliance.