Skip to content
VpnHood!

VpnHood! CLIENT

Linux requirements

Check your Linux machine before you install VpnHood! CLIENT or VpnHood! CONNECT: its distribution, its processor and, above all, a way to set the VPN's DNS. Without it, the app cannot connect.

Distributions

The apps run on x64 and ARM64. They install and start on these distributions; the ones built on them, and others with systemd and glibc, should also work:

DistributionVersions
Ubuntu22.04, 24.04, 26.04
Debian12, 13
AlmaLinux8, 9, 10
Rocky Linux9
CentOS Stream9, 10
Fedora43, 44
openSUSE Leap16.0
Amazon Linux2023
Arch LinuxRolling release

Not supported: Alpine and the other distributions built on musl instead of glibc. The app cannot run there.

What the system needs

  • Root access to install the app, and systemd, which runs its VPN service.
  • An administrator's account to use it: root, or a member of the sudo, wheel or admin group. A line in the sudoers file is not enough.
  • A TUN device for the VPN, which nearly every machine has.
  • A way to set the VPN's DNS: systemd-resolved, turned on, or resolvconf. Without one, the app cannot connect, and its error says what to do.
  • For the kill switch, nftables, which the installer adds, and cgroup v2. Without them, the app says so and does not connect while the kill switch is on.
  • For QUIC, MsQuic, which the installer adds. Where it cannot, as on Amazon Linux 2023, the app connects without QUIC.
  • For the window, a desktop. The installer adds the libraries the window needs. Without a desktop, you get the VPN service and the commands.

Processor

An ARM64 processor, or an x64 processor with SSE4.2 and POPCNT, as .NET 11 requires. Every x64 processor from the last ten years has them, but a virtual machine may be given a basic processor without them, which Linux names Common KVM processor. On such a machine the installer stops and says so.

To check an x64 Linux machine, run this on it:

grep -qw sse4_2 /proc/cpuinfo && grep -qw popcnt /proc/cpuinfo && echo Supported || echo "Not supported"

If it prints Not supported, ask your provider to change the machine's CPU type to host or x86-64-v2. If they cannot, choose another provider.

Next steps