OpenVPN Community Edition - powered by TurnKey can be improved, but not really because I think it already does the job excellently. Nothing comes to mind regarding needed improvements.
OpenVPN Community Edition - powered by TurnKey is very flexible, but there are features that would significantly improve day-to-day operations, especially in MSPs. The biggest improvement I would see is better centralized management, easier routing and network virtualization, more advanced built-in monitoring and reporting, simplified certificate lifecycle management, and stronger integrations with identity providers. One thing we often wish for is something similar to enterprise VPN dashboards where we can instantly see who is connected, which routes are active, failed authentication attempts, and tunnel health. Overall, the core VPN engine itself is solid, but most frustrations are really around management, visibility, scalability, and operational convenience rather than the tunnel functionality itself. The biggest friction point with OpenVPN Community Edition - powered by TurnKey is usually around configuration complexity and troubleshooting, especially in more complex client networks. I encounter issues whenever there are routing and subnet issues, DNS resolution problems, certificates and client configuration management challenges, limited centralized management in the community edition, or documentation dependency.
OpenVPN Community Edition - powered by TurnKey can be improved by increasing the session time of the OpenVPN token, which I believe is only available for 24 to 26 hours. After that, we need to enter our security code again to access it. It could be extended to two days or 48 hours for a single session.
All we are looking forward to is to know the configuration we have to follow if an N number of concurrent connections is required. For example, if it could have been 20 or 30, then what should be the OpenVPN Community Edition - powered by TurnKey server configuration. We need this recommendation to be available to us. The documentation from OpenVPN Community Edition - powered by TurnKey is absolutely good and does not require any changes. My only recommendation is that the configuration with the desired capacity of the number of users who intend to access the cloud tenant resources via OpenVPN Community Edition - powered by TurnKey should be given in their forum.
OpenVPN Community Edition - powered by TurnKey can be improved by looking forward to recommendations regarding compute sizing, which is necessary. I have seen multiple third-party solutions demanding configurations based on compute and memory aspects. However, what I have learned from OpenVPN Community Edition - powered by TurnKey is that it comes with minimal configuration, but I am always stringent about how many client VPN connections it can handle. There has to be some bifurcation regarding this. I have not experienced any access lag so far or any performance issues. I do not see any problems with the configurations or recommendations provided by OpenVPN Community Edition - powered by TurnKey for 100 or 200 users simultaneously, but I still foresee a need for some recommendations from OpenVPN Community Edition - powered by TurnKey regarding the number of user connections it can handle given certain configurations.
Learn what your peers think about OpenVPN Community Edition - powered by TurnKey. Get advice and tips from experienced pros sharing their opinions. Updated: June 2026.
OpenVPN Community Edition powered by TurnKey delivers reliable VPN solutions for secure remote connections, providing flexibility and robust performance. It suits tech-savvy users seeking efficient setup and management in various environments.
OpenVPN Community Edition powered by TurnKey offers a comprehensive VPN service that integrates seamlessly into existing IT infrastructures. Known for its high level of security, it allows users to create secure connections across different...
OpenVPN Community Edition - powered by TurnKey can be improved, but not really because I think it already does the job excellently. Nothing comes to mind regarding needed improvements.
OpenVPN Community Edition - powered by TurnKey is very flexible, but there are features that would significantly improve day-to-day operations, especially in MSPs. The biggest improvement I would see is better centralized management, easier routing and network virtualization, more advanced built-in monitoring and reporting, simplified certificate lifecycle management, and stronger integrations with identity providers. One thing we often wish for is something similar to enterprise VPN dashboards where we can instantly see who is connected, which routes are active, failed authentication attempts, and tunnel health. Overall, the core VPN engine itself is solid, but most frustrations are really around management, visibility, scalability, and operational convenience rather than the tunnel functionality itself. The biggest friction point with OpenVPN Community Edition - powered by TurnKey is usually around configuration complexity and troubleshooting, especially in more complex client networks. I encounter issues whenever there are routing and subnet issues, DNS resolution problems, certificates and client configuration management challenges, limited centralized management in the community edition, or documentation dependency.
OpenVPN Community Edition - powered by TurnKey can be improved by increasing the session time of the OpenVPN token, which I believe is only available for 24 to 26 hours. After that, we need to enter our security code again to access it. It could be extended to two days or 48 hours for a single session.
All we are looking forward to is to know the configuration we have to follow if an N number of concurrent connections is required. For example, if it could have been 20 or 30, then what should be the OpenVPN Community Edition - powered by TurnKey server configuration. We need this recommendation to be available to us. The documentation from OpenVPN Community Edition - powered by TurnKey is absolutely good and does not require any changes. My only recommendation is that the configuration with the desired capacity of the number of users who intend to access the cloud tenant resources via OpenVPN Community Edition - powered by TurnKey should be given in their forum.
OpenVPN Community Edition - powered by TurnKey can be improved by looking forward to recommendations regarding compute sizing, which is necessary. I have seen multiple third-party solutions demanding configurations based on compute and memory aspects. However, what I have learned from OpenVPN Community Edition - powered by TurnKey is that it comes with minimal configuration, but I am always stringent about how many client VPN connections it can handle. There has to be some bifurcation regarding this. I have not experienced any access lag so far or any performance issues. I do not see any problems with the configurations or recommendations provided by OpenVPN Community Edition - powered by TurnKey for 100 or 200 users simultaneously, but I still foresee a need for some recommendations from OpenVPN Community Edition - powered by TurnKey regarding the number of user connections it can handle given certain configurations.
I would like to get less updates from the solution.
The product's initial setup phase is not straightforward, making it an area where improvements are required.