This article describes installing Vinteo Server 40 on a supported open Linux distribution using a self-extracting .run installer.
.run file name with technical support. For Astra Linux Special Edition, release 1.8.4 is normally used. Another 1.8 release — only if support confirmed compatibility. In command examples the file name is written as srv-<version>.run.
Supported operating systems
Primary target platforms:
- Debian 13;
- Astra Linux Special Edition 1.8 — preferably 1.8.4.
The main installation method is the
.runfile. It starts the Vinteo installer, which configures package sources and installs the selected product components.
For a server without internet access, use the same file with install --no-change-apt and a prepared local OS mirror. The --no-change-apt option keeps the system APT sources unchanged.
What to prepare
Before running the installer, ensure the following:
- a supported OS that is installed and up to date;
- administrative access as
rootor an equivalent viasudo; - correct IP settings, DNS, and time synchronization;
- access to the selected OS repositories or a complete local mirror;
- free disk space for package download and component installation;
- the Vinteo Server installer file for the required version;
- the agreed licensing scheme (see Choosing a licensing scheme);
- on servers with an NVIDIA GPU — kernel header packages before running
.run(see the section below).
Check the OS state before you start:
cat /etc/os-release
uname -r
ip -br address
timedatectl status
apt-get update
apt-get check
df -hapt-get update and apt-get check must complete without errors. If the server uses a local mirror, the output must not attempt unreachable public addresses.
Kernel headers for GPU servers
This section applies only if the server has an NVIDIA GPU.
The NVIDIA driver is built for the running Linux kernel. The build needs kernel header packages (linux-headers). Without them:
- driver packages may still install;
- the kernel module is not built;
- after a reboot the GPU does not work.
The installer log often contains:
WARNING: No kernel headers were found, skipping module build.
In that case dkms status usually shows added, but you need installed. Another reboot alone does not fix it — install headers and rebuild first.
On Debian 13 (amd64), run as root before .run:
apt update
apt install "linux-headers-$(uname -r)" linux-headers-amd64"linux-headers-$(uname -r)"— headers for the kernel that is running now;linux-headers-amd64— so headers remain available after a Debian kernel update.
Before confirming the package install, review the APT change list: a new kernel may be pulled in with the headers. On a server without internet, these packages must be in the local mirror.
On Astra Linux, install headers from the OS repository agreed with support for the required kernel. Do not copy the Debian linux-headers-amd64 command to Astra — the package set is different.
You do not need to reboot right after installing headers. Reboot at the end if the Reboot section requires it.
Disk space
Free space is needed along the whole install path: the .run file, temporary extraction, the Vinteo package repository copy, product components, and OS data. Check each involved partition (volume), not only the total disk size.
The 2 / 4 / 10 / 32 GiB figures in the table are planning guidelines. They are not a hard minimum for every server. If the .run file is already on disk, you do not need to reserve the same amount of free space again for that file.
| Directory / file system | Preliminary free space | Purpose |
|---|---|---|
Directory with the .run file |
file size (guideline — 2 GiB) | installer file |
/tmp or selected TMPDIR |
4 GiB | package extraction |
/srv (/srv/vcs/repository) |
4 GiB extra | permanent package repository copy |
/usr (including /usr/vserver) |
10 GiB | binaries and dependencies |
/var (including /var/www) |
10 GiB | service data, APT cache and indexes |
/boot, if separate |
2 GiB | only if the kernel is updated |
/user-dir and recording directories |
case by case | configuration, recordings, media |
If /usr, /var, /srv, and the temporary directory share one partition, plan about 32 GiB free before downloading .run (excluding conference recordings and other user data). That partition must also hold the already installed OS.
During an update the installer may keep both the old repository /srv/vcs/repository and the new repository.new for a while. /srv must fit both sets of files at once.
/home or on a recordings disk does not help if /var or /usr is full. If directories are on different partitions, reserve space on each partition separately.
Before you start, check free space and which partition each path uses:
df -hT . / /usr /var /srv /tmp /boot
df -i . / /usr /var /srv /tmp /boot
findmnt -T /usr
findmnt -T /var
findmnt -T /srv
findmnt -T /tmp
findmnt -T /var/www
findmnt -T /var/lib/asterisk
findmnt -T /usr/vserverIf a directory does not exist yet, check its parent. df -i shows free inodes: gigabytes may remain while the system can no longer create files.
If /tmp is too small or is tmpfs (RAM), create a directory on disk and point the installer to it:
install -d -m 0700 /srv/vinteo-install-tmp
df -hT /srv/vinteo-install-tmp
df -i /srv/vinteo-install-tmp
findmnt -T /srv/vinteo-install-tmp
TMPDIR=/srv/vinteo-install-tmp ./srv-<version>.runIf the temporary directory and the repository are both on /srv, plan about 8 GiB free (4 GiB for extraction + 4 GiB for the new repository copy). During an update, space already used by the old repository copy remains occupied as well.
Obtaining the installer
Installer files are provided only through technical support: support@vinteo.ru. Use the file specified for the particular installation or update.
If the browser saved the archive with a .gz extension, rename it back to .run:
mv srv-<version>.gz srv-<version>.run
chmod +x ./srv-<version>.runInstallation with access to OS repositories
Step 1. Run the installer as root:
./srv-<version>.runStep 2. In interactive mode, select the product and licensing scheme. For production, network licensing net (NLS) is normally selected, followed by local or dedicated NLS setup. Choose Static / Dynamic only if technical support specified that scheme. Do not use a direct client connection to nls.vinteo.com for production.
Step 3. Before confirming the APT transaction, review the list of packages to install, upgrade, and remove. Ensure OS dependencies come from the expected OS repositories and Vinteo packages come from the installer repository.
Step 4. Confirm the installation and wait until it finishes without errors.
On an NVIDIA server, check the driver build before reboot:
dkms status
uname -rNVIDIA must show status installed for the kernel that will boot after reboot. added and built mean the module is not ready yet. If the kernel did not change, compare with uname -r. If APT installed a new kernel, check the line for that new kernel.
Installation without internet access
In a closed network, prepare a local mirror of a compatible Debian release in advance and verify apt-get update. For NVIDIA servers, include kernel headers for the DKMS build in the mirror.
Run the installer while keeping the system APT configuration:
./srv-<version>.run -- install --no-change-aptThe first -- separates self-extracting archive options: everything after it is passed to the Vinteo installer.
--no-change-apt, the installer in the default authoritative mode overwrites /etc/apt/sources.list and clears the /etc/apt/sources.list.d/ directory, then creates sources from its profile. This also affects administrator-added .list and .sources files. Moving local mirror settings from sources.list to sources.list.d alone does not protect them from deletion.
With --no-change-apt, the installer preserves /etc/apt/sources.list and third-party files in /etc/apt/sources.list.d/, while writing its own Vinteo source to /etc/apt/sources.list.d/vinteo.list. Do not use the name vinteo.list for OS mirror settings. Pass the option for both the initial installation and subsequent updates whenever you need to keep custom package sources.
Before running the installer, back up /etc/apt/, configure an accessible mirror of a compatible OS release with all required dependencies, and disable unreachable public sources in all APT source files. Verify that apt-get update and apt-get check complete without errors or requests to unreachable addresses.
The option does not skip apt-get update, dependency installation, or upgrades of already installed OS and Vinteo packages when updating a running system. It also does not disable existing public sources or restore settings replaced by an earlier run without the option: restore the required sources and check APT before running the installer again.
Reboot
A reboot is required if the installer reported it, or if any of the following were installed or updated:
- the OS kernel;
- an NVIDIA driver or DKMS module;
- system libraries that require an OS restart.
If none of these changed, a reboot only because Vinteo was installed is not required.
Do not reboot “to finish building the driver” if kernel headers were missing: install headers first, then run the installer, confirm dkms status shows installed, and only then reboot if this section requires it.
After a reboot, verify:
uname -r
ip -br address
dpkg --audit
apt-get check
systemctl --failedOn a GPU server, also confirm that nvidia-smi sees all installed GPUs.
Licensing setup
After installation, configure the scheme in preference order:
- Local NLS — client and NLS on the VCS host, NLS to Root NLS;
- Dedicated NLS — client to an NLS in the customer perimeter, NLS to Root NLS;
- Closed perimeter — NLS in the perimeter without Root NLS;
- Static or Dynamic — without NLS.
Scheme overview: Choosing a licensing scheme.
Test or pilot only: Public NLS (nls.vinteo.com without a local NLS).
License assignment and registration confirmation are performed by technical support (support@vinteo.ru).
First sign-in to the web interface
In deliveries with administrator bootstrap, the first sign-in credentials are written to /root/vinteo-bootstrap-admin. The web interface user is admin.
Open the web interface over HTTPS, sign in as admin with the temporary password from the file, and set a permanent password. Then sign out and verify sign-in again.
By default a self-signed certificate may be used — the browser will show a warning. Replacing it with a trusted CA certificate is done via Nginx files: HTTPS certificate.
Reissuing the temporary password
Use this if the temporary password was already consumed or the session was lost before the password change, and a permanent password has not been set yet.
Requirements: package installation has finished and the database responds. First check that the files used in the commands below exist on the server. If they do not, contact support@vinteo.ru — do not invent workaround commands.
set -a
. /etc/vcs/db.env
set +a
/usr/bin/php /usr/lib/server-db/bootstrap-admin.php --reissue
cat /root/vinteo-bootstrap-adminThe file contains the password. Do not include its contents in tickets, work logs, or screenshots.
Bootstrap credential is not in recoverable state, contact technical support. If installation stopped due to lack of disk space, fix that first.
Verifying the result
For an NVIDIA server, a practical order is:
- install kernel headers;
- run the
.runinstaller; - confirm
dkms statusshows installed; - reboot if required;
- confirm
nvidia-smisees all GPUs.
dpkg --audit
apt-get check
systemctl --failed
vinteostat -aFor a GPU server, also run:
dkms status
nvidia-smiSuccessful installation criteria:
dpkg --auditreports no half-configured packages;apt-get checkcompletes without dependency errors;- the main Vinteo services are active;
vinteostat -ashows the expected version and licenses;- the web interface is available over HTTPS;
- a test conference can be created and audio/video traffic passes;
- on an NVIDIA server:
dkms statusshows installed, andnvidia-smilists all GPUs.
Limitations
- Do not enable development repositories on a production server unless technical support instructs you to.
- Do not remove Vinteo packages with
apt purge --auto-remove“for a clean reinstall” — system dependencies may be affected. - Do not install an arbitrary NVIDIA driver version without checking compatibility with the OS, kernel, and Vinteo package set.
- Before updating a running 40.x system, save the configuration and read the notes for your version.
- If support issued a special installer set, follow their instructions for that delivery — do not apply one-off workaround steps to every 40.x install.