# Problems with clustering

**URL:** <https://forum.pritunl.com/t/problems-with-clustering/1538>\
**Category:** Pritunl VPN\
**Tags:** pritunl\
**Created:** [November 9, 2023, 7:05pm UTC](https://forum.pritunl.com/t/problems-with-clustering/1538 "2023-11-09T19:05:13Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Roalvi](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/r/8491ac/32.png) [@Roalvi](https://forum.pritunl.com/u/Roalvi)\
**Post date:** [November 9, 2023, 7:05pm UTC](https://forum.pritunl.com/t/problems-with-clustering/1538/1 "2023-11-09T19:05:13Z")

</div>

Hi all. We are Enterprise users and have encountered problems adding new nodes. Previously we had the following architecture: 2 Pritunl servers and 1 MongoDB server. They are all from the same provider in Germany and it worked great. Now we are trying to add several new servers in other countries, they connect to the database without problems and are displayed in the web interface, however, when we try to launch a VPN instance on them, we will receive an error like:  
Error on starting server: Non-200 response on starting the server body=500: Internal Server Error.  
We assume this may be due to the fact that the base is located far from the servers. Our assumption is based on the fact that when starting a VPN with a small number of routes, the server starts up every other time. However, if there are 10+ routes, it does not start at all. We tried various options for connecting the base - from an SSH tunnel to forwarding the base port to the outside. However, this did not affect the result in any way. Are there any ways to solve this problem?

---

<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:** [November 10, 2023, 1:00pm UTC](https://forum.pritunl.com/t/problems-with-clustering/1538/2 "2023-11-10T13:00:15Z")

</div>

Check the top right logs in the web console for a more detailed error message. If it was a database connection error it may only be shown in the `/var/log/pritunl.log` file for that host. If it is a server start timeout error this is a known issue with MongoDB 7, the database should be downgraded to MongoDB 6.

---

<div class="post-metadata">

**Author:** ![Roalvi](https://forum.pritunl.com/letter_avatar_proxy/v4/letter/r/8491ac/32.png) [@Roalvi](https://forum.pritunl.com/u/Roalvi)\
**Post date:** [November 10, 2023, 1:35pm UTC](https://forum.pritunl.com/t/problems-with-clustering/1538/3 "2023-11-10T13:35:49Z")

</div>

There are no errors specifically related to connecting to the database in the logs. Only an error starting the VPN instance. We are using the latest stable version of pritunl and mongodb version 5.0.
