# Pritunl server not accessible through VPN with more than 1 connection

**URL:** <https://forum.pritunl.com/t/pritunl-server-not-accessible-through-vpn-with-more-than-1-connection/80>\
**Category:** Pritunl\
**Tags:** pritunl\
**Created:** [April 20, 2022, 10:07am UTC](https://forum.pritunl.com/t/pritunl-server-not-accessible-through-vpn-with-more-than-1-connection/80 "2022-04-20T10:07:12Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pascal-hofmann](https://forum.pritunl.com/user_avatar/forum.pritunl.com/pascal-hofmann/32/226_2.png) [@pascal-hofmann](https://forum.pritunl.com/u/pascal-hofmann)\
**Post date:** [November 24, 2022, 2:18pm UTC](https://forum.pritunl.com/t/pritunl-server-not-accessible-through-vpn-with-more-than-1-connection/80/6 "2022-11-24T14:18:30Z")

</div>

We had issues with “Unable to assign ip address, pool full” when a user tried to connect with multiple devices after even after extending the network range of a server.

I checked the database and noticed that `pool_cursor` was set to the start of the network range, even though there were a lot of unused IP addresses in the network.

According to the source code it is never reset, unless you restart the server.

In order to avoid a restart of the server, I fixed this by running:

```auto
db.servers.update({'_id': ObjectId("SERVERID")}, {'$set': {'pool_cursor': null }});

```

---

_[View the full topic](https://forum.pritunl.com/t/pritunl-server-not-accessible-through-vpn-with-more-than-1-connection/80)._
