0.0.0.0:* users:(("python3",pid=715,fd=3))
```
No `openvpn` process is running either as no user can connect, so still failing healthcheck in that regard. I’m not sure how to connect directly as a test user to a specific server vs just the pool to try and mitigate this.
I can verify MongoDB connectivity with `pritunl logs` and though I haven’t had to do anything with licensing or server setup, I may have missed something in that setup process.
I’m pretty new to managing Pritunl and have inherited this quite old cluster so I really appreciate your help thus far.
---
### Author:  [@zach](https://forum.pritunl.com/u/zach)
#### Post date: [September 16, 2026, 11:50pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/6 "2026-09-16T23:50:21Z")
There should be a `pritunl-web` process check the output of `sudo journalctl -u pritunl-web` and `sudo systemctl status pritunl-web`. This service can’t be manually started, it must be started by the pritunl service during startup which provides the state data for the service. If the Systemd unit isn’t working running `sudo pritunl set app.web_systemd false` will run the process directly but this reduces the security isolation.
---
### Author:  [@ctrlv7887](https://forum.pritunl.com/u/ctrlv7887)
#### Post date: [September 17, 2026, 3:19pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/7 "2026-09-17T15:19:21Z")
Yep, that service is dead. Seeing this after setting the `app.web_systemd false`:
```auto
systemctl status pritunl-web.service
× pritunl-web.service
Loaded: loaded (/etc/systemd/system/pritunl-web.service; static)
Active: failed (Result: exit-code) since Thu 2026-09-17 15:15:25 UTC; 1min 14s ago
Duration: 28ms
Process: 199143 ExecStart=/usr/bin/pritunl-web (code=exited, status=2)
Main PID: 199143 (code=exited, status=2)
CPU: 24ms
[199143]: time="2026-09-17T15:15:25Z" level=info msg="main: Starting HTTP redirect server" port=80
[199143]: time="2026-09-17T15:15:25Z" level=error msg="main: Redirect server error" error="listen tcp 0.0.0.0:80: bind: address already in use"
[199143]: time="2026-09-17T15:15:25Z" level=info msg="main: Starting HTTPS server" port=443
[199143]: time="2026-09-17T15:15:25Z" level=error msg="main: Server error" error="listen tcp 0.0.0.0:443: bind: address already in use"
[199143]: panic: listen tcp 0.0.0.0:443: bind: address already in use
[199143]: goroutine 1 [running]:
[199143]: main.main()
[199143]: /go/pkg/mod/github.com/pritunl/pritunl-web@v0.0.0-20260501212631-b04fc4af0818/main.go:257 +0xcc5
systemd[1]: pritunl-web.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
systemd[1]: pritunl-web.service: Failed with result 'exit-code'.
```
Is it worth killing the node and trying again?
---
### Author:  [@ctrlv7887](https://forum.pritunl.com/u/ctrlv7887)
#### Post date: [September 17, 2026, 3:36pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/8 "2026-09-17T15:36:57Z")
Interestingly, our older nodes on centos7 do not have a pritunl-web.service:
```auto
Unit pritunl-web.service could not be found.
```
---
### Author:  [@zach](https://forum.pritunl.com/u/zach)
#### Post date: [September 17, 2026, 10:08pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/9 "2026-09-17T22:08:24Z")
Run `sudo netstat -tulpn` to find what is using port 443 and stop that service or change the port for the Pritunl web server with the command `sudo pritunl set app.server_port 443`. This will change the port on all hosts.
Older versions of the software did not use the isolated Systemd unit.
---
### Author:  [@ctrlv7887](https://forum.pritunl.com/u/ctrlv7887)
#### Post date: [September 18, 2026, 4:22pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/10 "2026-09-18T16:22:38Z")
```auto
sudo netstat -tulpn | grep 443
tcp6 0 0 :::443 :::* LISTEN 264294/pritunl-web
```
Curious. The web and Pritunl services are definitely in a weird state. Looks like the Pritunl daemon is started and ports 80 and 443 are fine, but then the -web service thinks they’re already in use.
I think I’m going to attempt a reinstall and then check to see whether that port change command will affect the rest of my cluster here. Not sure how the node got into this state really.
---
### Author:  [@ctrlv7887](https://forum.pritunl.com/u/ctrlv7887)
#### Post date: [September 18, 2026, 6:02pm UTC](https://forum.pritunl.com/t/new-pritunl-host-rebooting-every-hour/3849/11 "2026-09-18T18:02:35Z")
I think we can close this one - found old non-Pritunl-related VPNhealthcheck scripting that was causing the OOM rebooting issue and dropping from our Route53 cluster, and a reinstall/reconfig got ports and everything started up correctly.
Now on to testing whether I can actually get users connected. Thanks again Zach.