# Pritunl Self Hosted in AWS

**URL:** <https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706>\
**Category:** Pritunl VPN\
**Created:** [February 3, 2026, 4:39pm UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706 "2026-02-03T16:39:58Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![mmughal](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/m/58956e/32.png) [@mmughal](https://forum.pritunl.com/u/mmughal)\
**Post date:** [February 3, 2026, 4:39pm UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706/1 "2026-02-03T16:39:58Z")

</div>

We have been hosting multiple Pritunl servers for the past 2 years. Two in AWS and two in our Data Centres.

Since 05:00 GMT our Pritunl instances hosted in AWS showing error messages and we are no longer able to connect to the profiles that they host. We can connect to different profiles hosted by Pritunl instances in our Data Centres.

The EC2 instances have been rebooted, rolled back to a previous instance of Pritunl, checked connectivity to Mongo Atlas DB.

The errors we see from the AWS instances are as follows

AttributeError: ‘NoneType’ object has no attribute ‘vxlan\_addr’  
UnboundLocalError: local variable ‘network’ referenced before assignment

”systemctl status pritunl.service” shows as started.

Any assistance would be greatly appreciated.

Thanks.

---

<div class="post-metadata">

**Author:** ![Nicolas](https://forum.pritunl.com/user_avatar/forum.pritunl.com/nicolas/32/27_2.png) [@Nicolas](https://forum.pritunl.com/u/Nicolas)\
**Post date:** [February 3, 2026, 7:06pm UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706/2 "2026-02-03T19:06:39Z")

</div>

probably issue with last release v1.32.4512.98 if your server run on ubuntu as described here [Issue with new release - #3 by zach](https://forum.pritunl.com/t/issue-with-new-release/3695/3)

---

<div class="post-metadata">

**Author:** ![mmughal](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/m/58956e/32.png) [@mmughal](https://forum.pritunl.com/u/mmughal)\
**Post date:** [February 4, 2026, 8:30am UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706/3 "2026-02-04T08:30:11Z")

</div>

We are using Alma Linux in all deployments for Pritunl.

---

<div class="post-metadata">

**Author:** ![Oliniusz](https://forum.pritunl.com/user_avatar/forum.pritunl.com/oliniusz/32/1441_2.png) [@Oliniusz](https://forum.pritunl.com/u/Oliniusz)\
**Post date:** [February 4, 2026, 11:47am UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706/4 "2026-02-04T11:47:41Z")

</div>

The same for me on Oracle 9 with stable:

- `pritunl-1.32.4512.98-1.el9.oraclelinux.x86_64`

and unstable:

- `pritunl-openvpn-2.6.17-1.el9.oraclelinux.x86_64`.

I needed to roll it back to the previous release that was working:

- `pritunl-1.32.4400.99-1.el9.oraclelinux.x86_64`.

The logs:

```auto
[vpn][2026-02-04 10:43:01,333][INFO] Signing certificate...
[vpn][2026-02-04 10:43:01,636][ERROR] Server error occurred while running
Traceback (most recent call last):
  File "/usr/lib/pritunl/usr/lib/python3.9/site-packages/pritunl/server/instance.py", line 1453, in reserve_route_advertisement
'vxlan_addr': self.vxlan.vxlan_addr,
AttributeError: 'NoneType' object has no attribute 'vxlan_addr'

```

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [February 4, 2026, 11:27pm UTC](https://forum.pritunl.com/t/pritunl-self-hosted-in-aws/3706/5 "2026-02-04T23:27:19Z")

</div>

This is being fixed in the v1.32.4528.97 release. This will be on the [**unstable repositories**](https://docs.pritunl.com/kb/vpn/repositories#unstable-repositories) later tonight.