OPENVPN CLOUD IS LIVE: TRY TODAY FOR FREE
Official OpenVPN Connect client program

OpenVPN Connect for Mac OS

This is the official OpenVPN Connect client software for Mac OS developed and maintained by OpenVPN Inc. This is the recommended client program for the OpenVPN Access Server. The latest version of OpenVPN Connect client for Mac is available on our website.

If you have an OpenVPN Access Server, it is recommended to download the OpenVPN Connect client software directly from your own Access Server, as it will then come preconfigured for use. The version available here contains no configuration to make a connection, although it can be used to update an existing installation and retain settings.

Download OpenVPN Connect v3

sha256 signature: 0fcab3724cc71d1b2fc1cf645982fb7b70a5d860f5a8eadf03bf9d01ca973ca2

For mac OS versions titled Mavericks, Yosemite, El Capitan, Sierra,
High Sierra, Mojave, and Catalina.



Previous generation OpenVPN Connect V2 is available here:

Download OpenVPN Connect v2.7.1

sha256 signature: 058a8d2c5b3817722a0474eb004e77d551726e710a4fb17c4fa34a81faa6fa2a

The Interface

Our latest line of OpenVPN Connect software available for the major platforms features a new and improved user interface, making the experience of installing and using the OpenVPN software a snap. With an easy to use import feature you can import profiles straight from your OpenVPN Access Server or just import a saved profile from disk.

Frequently Asked Questions

Yes, you may continue to use both v2 and v3 on the same connect device and import the profiles desired into each. If you like, you can run either one or both.

No, the client cannot connect to multiple servers at once. It does support multiple connection profiles, giving you the option to switch easily from one server to the next, but you can only be connected to one at a time. This is by design, to prevent unexpected traffic paths when connecting to multiple VPN servers at the same time. If you are a system administrator and you require a complex setup where multiple connections are active at the same time, there is the option to use the open source community OpenVPN client software available from our website.

The OpenVPN client v1 was called “OpenVPN Desktop Client” and is no longer available. It is also not safe to use this anymore as it hasn’t been maintained for many years. It was replaced with the OpenVPN client v2. The OpenVPN client v2 is called “OpenVPN Connect Client” and has been in use for many years. It is still available from our website and offered in the OpenVPN Access Server client web interface itself. The OpenVPN client v3 is called “OpenVPN Connect” and is the latest generation of our software. It is available on our website as a beta version, and will be included soon in Access Server releases.

This is the official OpenVPN Connect software for Windows workstation platforms developed and maintained by OpenVPN Inc. This is the recommended client program for the OpenVPN Access Server. The latest versions are available on our website. If you have an OpenVPN Access Server, you can download the OpenVPN Connect client software directly from your own Access Server, and it will then come pre-configured for use. The version available here contains no configuration to make a connection, although it can be used to update an existing installation and retain settings.

  1. Download the DMG file
  2. Open the file and double click the box icon to begin the installation.
  3. Give permissions to install on your Mac by entering your credentials when prompted.
  4. Click Close when you get the “installation was successful” message.
  5. You can move or keep the OpenVPN Connect installer, simply choose the appropriate action when prompted.
  6. Open the Launchpad app from the app bar and click on OpenVPN Connect to send it to your app bar.
  7. Click on the icon to start the Onboarding Tour.
  8. Review how to import a profile from a server by entering the Access Server Hostname and credentials or uploading a profile from your computer.
  9. Agree to the data collection use and retention policies after reviewing them.
  10. Import a profile, either from the server or from file.

Directions found here for installing the client directly from Access Server for your macOS computer. This install is preconfigured with your connection settings from your server.

  1. From the OpenVPN Connect UI, choose “Import from Server”.
  2. Enter your Access Server Hostname, Title, Port (optional), and your credentials–username and password.
  3. Click Add.
  4. If you choose to Import autologin profile, it is less secure, but you won’t need to re-enter credentials.

  1. Choose “Import from File”.
  2. Drag and drop a .OVPN file or click on Browse to navigate to the location on your computer.
  3. The message displays that the profile is successfully imported and displays the hostname and the title. You can change the title if desired.
  4. Click on Add to complete the import.

Layer 2 bridging (TAP) is no longer supported. Switch over to TUN Mode to resolve this issue.

OpenVPN Access Server starts with a self-signed certificate. With this, you will receive warnings from your web browser about the site not being secure as well as a certificate error when importing a profile with the Connect Client. You can simply override the warnings or add an exception for your web browser. To resolve this, you can set up a DNS host name that resolves to the public address of your Access Server and install a valid SSL certificate that corresponds to that DNS host name. Going forward, you would use that hostname to access your server instead of the IP address. This is also the recommended method as validated SSL certificates can only ever function with a valid public DNS hostname.

Your Access Server Hostname is the address at which your Access Server can be reached. For example it could be https://vpn.yourcompany.com/. If a DNS hostname is not set up, it is also possible to specify the IP address where your Access Server. For example:https://55.193.55.55 Your credentials are your username and password. You may need to get that information from your Access Server administrator if you don’t know it.

Title is the name for the profile. It is automatically defined as the username with the hostname or IP address(example: user1@hostname). It differentiates between multiple profiles. You can define it manually as well. The title can be anything you want is just so you can see which profile is which.

Choosing this option allows you to import an autologin profile with the address and credentials for your Access Server, then simply start the connection with the tap of a button. You would not need to re-enter credentials each time you connect. The autoprofile itself contains an embedded secure certificate that identifies and authorizes your connection automatically. It is an optional setting on the OpenVPN Access Server that the administrator of the server can choose to make available to you. If you find you cannot import the autologin profile, your administrator may not have allowed autologin through user permissions.

During investigation of a vulnerability called VORACLE, it was found that using compression to make the data that goes through the VPN tunnel smaller, and thus faster, has an adverse effect on security. To learn more about this see our security notification on our website regarding the VORACLE attack vulnerability. In order to protect our customers, we are disabling compression by default. Some servers of the open source variety can be configured in such a way that the client must do compression, or else the client may not connect successfully. In such a case, you should get the server updated to disable compression. But we understand that this is not always possible, and you may need to be able to connect to such a server. In that event you can go into the settings and re-enable compression.

Downloading and installing (for Client Connect v2)

Got any questions or suggestions regarding our OpenVPN Connect software? Drop us a message here!

This site is protected by reCAPTCHA and the Google
Privacy Policy and Terms of Service apply.

Release Notes v3

Release date: 26 August, 2020

  • Please note that current 3.2.2 app version is the last version that still supports OS X Mavericks
  • Added reporting UV_ASCLI_VER and UV_PLAT_REL values to the VPN server.
  • Fixed not prompting user for certificate approval under certain conditions.

Release date: 7 July, 2020

  • Fixed incorrect hardware address reporting.

Release date: 26 June, 2020

  • This is now a stable release and no longer considered beta software.
  • As part of the transition from Mbed TLS to OpenSSL the list of negotiable TLS cipher suites no longer includes weak cipher suites that lack forward secrecy support (DH/ECDH)
  • Switchover from Mbed TLS library to OpenSSL library
  • Support of TLS 1.3 version
  • Support signing with RSA-PSS signatures during TLS handshake
  • Update of OpenVPN3 library to OpenVPN core 3.5.6 version
  • Improved stability and performance

  • New profile import flow with WebAuth support
  • Added EULA license during installation
  • Added .ovpn file association
  • Added possibility to connect without external certificate when the client certificate is not required
  • Fixed app crash when UI stucks with blank screen
  • Fixed multiple re-connections in sleep mode
  • Fixed connection with DUO authentication service
  • Fixed connection via server-locked profile with 2FA
  • Fixed issue with DNS configurations after disconnect
  • Fixed proxy basic authentication
  • Fixed issue with long client-side scripts

  • Fixed a problem where the program would not respond properly during network unavailability
  • Fixed profile import with server certificate expired or self-signed – added ability to accept or reject such certificate despite this problem
  • Fixed password clearing during profile edit
  • Fixed parsing of ca.crt as a separate file
  • Fixed auth fail when username is not locked Showing proper core version in the connection logs
  • Added descriptive error message for connection attempt via TAP-based profiles

  • Fixed behavior of connection timeout with network unavailable
  • Fixed connection logic via server-locked profile for users without auto-login privilege
  • Fixed profiles sorting in tray by last connected
  • Fixed static-challenge response logic
  • Added confirmation on dialogs by enter key
  • Added custom error message for users who trying to import auto-login profile without privilege
  • Changed tray icon in order to show VPN connection status
  • Changed order of settings in tray to be more logical
  • Updated installer texts so the product name is mentioned properly

  • New unified UI with 2 color scheme options
  • Dropped support of MD5 algorithm
  • Disabled tunnel compression by default (could be enabled back in the app settings)
  • Ability to add proxies for connection from within the app
  • Ability to manage external certificates directly from within the app (except in Windows 7 for the moment)
  • Separate screen with extended statistics of connection session
  • Log File with options to pause/resume, clear and save logs for sharing
  • Plenty of other settings like reconnect on reboot, seamless tunnel, IP/TLS versions etc.
  • Dropped support for macOS 10.8 Mountain Lion. Version 10.9 and higher are supported.

Release Notes v2

  • Added multi-factor support for the dynamic challenge/response model
  • Added support for dark/light mode in macOS
  • Updated MbedTLS to 2.7.13 to resolve a security issue (CVE-2019-18222)
  • Improved round-robin DNS server exclusion route handling
  • Resolved some various other minor stability issues

  • Resolved a problem where reconnect would fail on a round-robin DNS hostname as server address in combination with full-tunnel redirection.

  • Added DHCP option PROXY_AUTO_CONFIG_URL capability for proxy auto configuration (PAC) in the operating system. It is now possible to do for example:
  • push “dhcp-option PROXY_AUTO_CONFIG_URL (url to proxy PAC settings file)”
    • Split-DNS behavior on macOS was markedly different from our other OpenVPN Connect software programs, and this has now been corrected.

  • Fixed and improved platform and client version reporting to the server

  • mbedTLS: fix incompatibility with PKI created by OpenSSL 1.1
  • mbedTLS: add support for ECDSA
  • mbedTLS: updated to fix CVE-2018-0487 vulnerability.
  • Issue OpenVPN client showing ‘no VPN servers’ when a connection profile with an excessively long server host name was loaded is now fixed.
  • TLS key refresh (TLS soft reset) connection interruption when using –opt-verify is now fixed.

  • Failure to launch OpenVPN Connect Client on macOS version 10.11.6 has now been fixed.

  • The .dmg installer file is now properly signed and can still bundle profiles at the same time.