Sometimes OpenVPN Access Server is difficult to connect to, and in our company, we don't know why it is difficult. The product may not connect if we lose connection at times. There are certain shortcomings in the product's stability that need improvement.

In general, I want to improve the connect connectivity of the solution since I sometimes face stability issues.

The logs should be made easier to read. If there is an issue, it takes me a while to find it in the log.

The product’s connectivity is very slow. It could be faster.

The stability of the solution could improve.

The stability of the OpenVPN Access Server has room for improvement.

I haven't had issues with the solution. It's a good product. 

I'd like the solution to have more access points and more speed. 

We'd like the solution to continue to improve security. We'd like security over the network lists related to OpenSense. 

I'd like to have more control over the users when they are accessing the network. I'd like to know everything they've done while they are on the network. 

One improvement I would like to see in OpenVPN is better adaptability in certain geographical areas, like Asia, where the traffic can face blocks. Addressing this issue would enhance the overall performance, especially for data transfer in those regions.

The connections could be faster and more stable.

It could be faster. It could also be more stable.

There sometimes is an incompatibility between some VPNs. 

The product is fully customized through configuration files, which is all achieved through manual data entry. This is where it becomes unattractive. If there was a Graphical User Interface to help streamline the configuration, I believe OpenVPN would probably venture more into the non-geek realm as it were. What I mean by this is, if there was a form-driven configuration process, like a "File -> Settings" kind of thing, where the end user can enter data into fields to specify the connection specifics, e.g. hostname/IP Address, protocols, etc. that could be written into the config file in the background, similar to what you see in YaST over in openSuSE in some of the services area, etc., and basically foolproof the VPN configuration, you may see more GUI-oriented folks using OpenVPN. Of course in saying this, I anticipate what's going to happen: "Well, give it a try, Elliott!" I'd love to, but my programming skills aren't there yet - I'm a "Edit the file" guy...

The interface can be more user-friendly.

The stability had room for improvement.

The scalability has room for improvement.

This solution should improve the connection speed and the user interface. The stability of this solution should be improved as well.

In the next release, I would like to see the user interface become more user-friendly.

You do need expertise in implementation if you do the initial setup yourself. As it is open-source, if you run into issues, there is nobody available to help you. 

We can have more interfaces with the Active Directory. For example, if you want to integrate, it's not really working very well as an authentication method. 

Security-wise it's using good protocols like SecureONE, similar to AnyConnect. However, implementation-wise for the interfacing to the AD and interfacing to the Authenticators, it's a bit difficult. We had updated this a year before, and we had to revert it back to work with Google Authenticator.

OpenVPN Access Server needs to have fewer updates. 

Working on a faster connection might be a good idea for the product's next release.

They should make the solution more secure by adding some firewall functionalities.

There is always room for more security features.

I would like more frequent updates.

The solution can be more compatible with different operating systems.

The interface could be a little bit better in future iterations. 

They may have this already, but it would be nice to be able to get more notifications if a site drops unexpectedly.

It would be nice with all these features, if they could send some examples of each one; just small sample scripts to look at and say, "Oh okay, I could expand on this." That would help us a lot.

One area for improvement in OpenVPN is the ability to selectively terminate connections. If the program could list active connections and provide an option to delete or kill them, it would be a useful feature. This would save users the trouble of having to restart the entire program each time they need to terminate a connection.

The user interface that we had to implement. I would like to see a simpler interface, so that we can make the connection between the local network using the LAN IP.

Also, I would be more happy with the idea of licensing to have a reduced price with longer, grouped, annual fees. We have a lot of other software that does the same thing. It's a little higher price if you're going with a shorter stint, but there's a reduction in price for three- and five-year contracts.

I would like to see continued advanced security implementation.

We would like to be able to access the parts of the network that belong to other virtual LANs, which is not currently possible. For example, if an organization has different VLANs for sales, developers, and production, then we can only connect and view one of these segments. If you can access sales then you will have visibility of that particular subnet and not be able to see the developer VLAN resources.

The security needs to be improved because it was a complaint that our customers had. I'm not sure exactly what the specific issue is, other than they told us that it was not compliant with their organizational policies.

It is not possible to scale this solution horizontally, which is something that should be improved. They could allow multiple instances to run in different zones, synchronizing with each using a round-robin scheduler.

It would be great if they added intrusion prevention and detection (IPS/IDS) features. If they had these then there would be less need to use other products, such as firewalls. It would allow everything to run under one umbrella with centralized control.

There was one annoying feature where we had to disable and enable the user. I cannot remember what it was exactly, but I think it was for a password lockout. It would be nice if there was a checkbox, or something, in the web interface to allow you to unlock a user whose password was locked. 

The performance could be a bit better. The stability could always be enhanced. 

When there are too many concurrent users trying to connect at the same time, there may be a bit of a bottleneck. When all people would like to reconnect to the VPN at the same time, the performance and availability of the solution could be better.

I want the tool to be faster. We have experienced connectivity issues while using OpenVPN and FortiClient. 

Open VPN Access Server could be more user-friendly.

The upgrade path from older versions was more difficult than we wanted to tackle, so we ran an older version of the software for longer than I wanted. Patching, updating, and migrating to newer versions was a problem for us. That said, we were on a rather old version that I inherited yet it worked rock solid.

Some of the issues we faced were things like, if someone's key is not working, or if we had to remove someone's permission from it, or maybe an employee left the company and we had to take their key out. That seemed a little bit more complicated than it had to be.

Also, I think right now the GUI part of it is locked out behind the pay wall. It could use something that gives it a very basic, minimal, graphic interface for logging in, for the community version. That would probably be a good step forward.

Maybe provide a GUI or Web UI to manage users. Today these features are in the Pro Edition or are done by scripts.

The server configuration file needs to be improved, it's the biggest problem in the configuration process. I would also like the product's routing to be easier.

At the moment, I am not working too closely with the product.

There is occasionally some instability but that is due to issues with our internet connection, and is not related to the product. 

The scalability of the solution could be improved.

It could include a configuration wizard so that users who do not follow instructions well can configure a connection.

Better GUI.

Also, we switched more to Cisco AnyConnect due to the Win 10 stability issues.

The high availability deployment is not very straightforward. They can make it simpler. 

OpenVPN does not support some of the additional protocols that Pulse Secure and Cisco AnyConnect support. They can include support for these additional protocols.