Documentation/Connecting/Your server by hand/If Veli by hand does not install·3 / 3

If Veli by hand does not install

Common install errors and what to do about them.

“Port 443 is already taken by another program”

A website or another VPN holds the port. The install names the program and touches nothing. Install Veli on another port: sudo veli install --port 8443.

“Ubuntu, Debian and systems based on them… are supported”

The server's system is not one of those at the top of this article. Most hosts change the system in their panel by reinstalling the server — its data is erased. Pick Ubuntu or Debian and paste the line again.

“The server has no /dev/net/tun”

The server is an OpenVZ or LXC container without TUN. Turn TUN on in the host's panel, or ask its support to, then install again.

“The server has no IPv4, only IPv6”

Veli takes connections over IPv4. Add an IPv4 address to the server in the host's panel, or take a server that has one.

A device does not connect

Run sudo veli doctor: it says where things are stuck. If your hosting has a firewall of its own in its control panel, open Veli's port there, TCP and UDP: the server's own firewall the command sets up itself. Also look at sudo veli status — whether Veli works and gets out to the internet.

“The QR is wider than the window”

Widen the terminal window or make the font smaller and show the code again: sudo veli show laptop. Or open the link in Veli on a computer.

“Could not download the Veli program”

The server cannot reach our site. Install Veli from files brought from a computer — as in “If the server cannot reach our site” below.

“sudo: veli: command not found”

This happens on Rocky Linux, AlmaLinux and CentOS: sudo there does not look for programs in /usr/local/bin, where veli lives. Write the full path — sudo /usr/local/bin/veli status — or log in as root and call just veli.

If the server cannot reach our site

Sometimes a server cannot download files from our site — a server in Russia, for example. Then download two files to your computer and move them to the server.

The server's CPU
  1. Download to a computer

    The veli command and the Veli program for the server. Any computer where our site opens will do.

    veli-x86_64veli-node-x86_64.gz
  2. Move them to the server

    With scp from the computer, for example — put the server's address in place of “address”.

    On your computer
    scp veli-x86_64 veli-node-x86_64.gz root@address:
  3. Install

    Paste the line on the server: it checks the command's file and installs Veli from the program you brought. The command checks the program's signature itself.

    On the server
    echo "2e39f2aa4a21b91535399f881de4cb76847c0a5195b82aab50fbd85f19e0be15  veli-x86_64" | sha256sum -c &&
      chmod +x veli-x86_64 &&
      $( [ "$(id -u)" = 0 ] || echo sudo ) ./veli-x86_64 install --from veli-node-x86_64.gz

Such a server updates the same way: download the new version's files from this page, move them over and run the new command with update instead of install. It takes the place of the old one.