IVPN for Desktop (Windows/macOS/Linux)
IVPN for Desktop is the official IVPN app for desktop platforms. Some of the features include: multiple protocols (OpenVPN, WireGuard), Kill-switch, Multi-Hop, Trusted Networks, AntiTracker, Custom DNS, Dark mode, and more.
IVPN Client app is distributed on the official site www.ivpn.net.
- About this Repo
- Security Policy
About this Repo
This is the official Git repo of the IVPN for Desktop app.
The project is divided into three parts:
- Daemon is a core module of IVPN software built mostly using the Go language. It runs with privileged rights as a system service/daemon.
- UI is a Graphical User Interface built using Electron.
- CLI is a Command Line Interface.
These instructions enable you to get the project up and running on your local machine for development and testing purposes.
npm; nsis2; Build Tools for Visual Studio 2019 ('Windows SDK 10.0', 'MSVC v142 C++ x64 build tools', 'C++ ATL for latest v142 build tools'); gcc compiler e.g. TDM GCC; Go 1.13+; Git
npm; Xcode Command Line Tools; Go 1.13+; Git
npm; packages: FPM, curl, rpm, libiw-dev; Go 1.13+; Git
Instructions to build Windows installer of IVPN Client software (daemon+CLI+UI):
Use Developer Command Prompt for Visual Studio (required for building native sub-projects).
git clone https://github.com/ivpn/desktop-app.git cd desktop-app/ui/References/Windows build.bat
Compiled binaries can be found at:
Instructions to build macOS DMG package of IVPN Client software (daemon+CLI+UI):
git clone https://github.com/ivpn/desktop-app.git cd ivpn/desktop-app/ui/References/macOS ./build.sh -v <VERSION_X.X.X> -c <APPLE_DevID_CERTIFICATE>
Compiled binary can be found at:
Instructions to build Linux DEB and RPM packages of IVPN software ('base' package: daemon + CLI):
git clone https://github.com/ivpn/desktop-app.git cd desktop-app/cli/References/Linux/ ./build.sh -v <VERSION_X.X.X>
Compiled packages can be found at
Manual installation IVPN daemon on Linux
Sometimes it is required to have the possibility to install IVPN binaries manually.
It's easy to do it by following the rules described below.
The ivpn-service is checking the existing of some required files (all files can be found in the repository)
VirtualBox:/opt/ivpn/etc$ ls -l total 52 -r-------- 1 root root 2358 May 25 16:50 ca.crt -rwx------ 1 root root 113 May 25 16:50 client.down -rwx------ 1 root root 1927 May 25 16:50 client.up -rwx------ 1 root root 5224 May 25 16:50 firewall.sh -rw------- 1 root root 21524 May 26 20:52 servers.json -r-------- 1 root root 636 May 25 16:50 ta.key
- Build the current project to get 'ivpn service' and 'ivpn cli' binaries.
- Create folder
- Copy all required files (see above).
Note! Files owner and access rights are important.
- Now you can start compiled service binary from the command line (just to check if it works).
Note! The service must be started under a privileged user.
Info You can use the command line parameter
--loggingto enable logging for service.
4.1. Simply run compiled ivpn-cli binary to check if it successfully connects to the service (use separate terminal).
- If everything works - you can configure your environment to start ivpn-service automatically with the system boot (we are using systemd for such purposes)
Instructions to build Linux DEB and RPM packages of IVPN software 'UI' package:
git clone https://github.com/ivpn/desktop-app.git cd desktop-app/ui/References/Linux ./build.sh -v <VERSION_X.X.X>
Compiled packages can be found at
Note! It is required to have installed IVPN Daemon before running IVPN UI.
Project is using Semantic Versioning (SemVer) for creating release versions.
SemVer is a 3-component system in the format of
x stands for a major version
y stands for a minor version
z stands for a patch
So we have:
If you are interested in contributing to IVPN for Desktop project, please read our Contributing Guidelines.
If you want to report a security problem, please read our Security Policy.
This project is licensed under the GPLv3 - see the License file for details.
See the Authors file for the list of contributors who participated in this project.
See the Acknowledgements file for the list of third party libraries used in this project.