Hi there -
I’m working on upgrading an old Pritunl cluster from CentOS7 to Alma9, which is actively hosting our enterprise users.
We have less than 10 hosts on centos7 including a dedicated web console across various aws regions (Pritunl v1.30.3343.47), and I’ve added an Alma9 host to the cluster with upgraded Pritunl version (v1.34.4681.89) to attempt to start a process of upgrading OSes with no downtime to the user.
However, this new node is restarting every hour and will not accept new user connections, even though I have successfully granted the node access via IP to the mongodb, and a command like pritunl logs shows logs from other hosts across the cluster. All hosts are served via a single public IP hostname and live within the same local IP space.
The restart looks like:
[INFO] Starting server
version = "1.34.4681.89"
python_version = "3.12.13 (main, Jul 8 2026, 12:24:28) [GCC 11.5.0 20240719 (Red Hat 11.5.0-14)]"
ssl_version = "OpenSSL 3.5.5 27 Jan 2026"
selinux_context = "system_u:system_r:unconfined_service_t:s0"
web_auth_strict = true
and
systemd[1]: Stopping Pritunl Daemon...
systemd[1]: pritunl.service: Deactivated successfully.
systemd[1]: Stopped Pritunl Daemon.
systemd[1]: pritunl.service: Consumed 1.656s CPU time, 99.3M memory peak.
systemd[1]: Started Pritunl Daemon.
pritunl_pid_start.sh[40598]: time="2026-09-10T22:55:42Z" level=info msg="main: Starting HTTP redirect server" port=80
pritunl_pid_start.sh[40598]: time="2026-09-10T22:55:42Z" level=info msg="main: Starting HTTPS server" port=443
Any pointers in the right direction would be greatly appreciated as I’m not quite seeing anything relevant in the docs. Please let me know if I can provide more context.
Thanks in advance!