[LINUX] VRS X Setup Guide
Pre-start checklist
Makewaking the Linux beast, make sure yourOSsystemhasmeetskernelthe basic requirements:-
Kernel 5.0 or newer
Check it with:
uname -r MakesureOpenSSL 1.1.1 or OpenSSL 3.
0+x(supportingwith TLS 1.2/1.3)3issupportinstalled.Check it with:
openssl version
SudoNoissudonot necessaryneeded tostartrunVRSVRSX.XSudoup,entersbutthetochatsetonlyupforsystemd servicesystemd.-
Download the Linux zip
filepackage from the linkgivenprovided in the e-mail, forexampleexample:linux-arm64.zipUse the
linux-arm64package for ARM64 machines, for example Raspberry Pi 4/5 or other ARM64 devices.Use the
linux-x64package for Intel/AMD 64-bit machines. -
Unzip the
filepackage:using commandunzip linux-arm64.zip(or -x64 ifOr, on Intel/AMD
machine)machines:unzip linux-x64.zip -
Enter the
directoryextractedusingdirectory:commandcd linux-arm64(or -x64 ifOr, on Intel/AMD
machine)machines:cd linux-x64 -
Make the binary
executableexecutable:using commandchmod +x VRSX -
Start
itVRSX.up:Desktop mode:
./VRSXforHeadless
desktopmode:version,./VRSX --headlessfor headless mode EnterOpen VRSX in your browser:
http://IP.OF.YOUR.MACHINE:8085andprovideExample:
licencehttp://192.168.100.100:8085-
Activate VRSX using the license key
providedavailable under the “My Account” section inanADS-B.ProemailRadarView.
Your instance is ready to go!
Set up a systemd service, sudo is
necessary!necessary hereAssuming,If you want VRSX to start automatically after boot, you can create a systemd service.The example below assumes:
- your Linux username is
youruser - VRSX is located in
/home/youruser/linux-arm64 - you are running the ARM64 version
If you are using Intel/AMD, replace
linux-arm64withlinux-x64.If your username is not
youruser, replaceyouruseruser on machine and VRS X is unzipped intowith yourhomerealdirectory,Linuxforusername.exampleTo check your username, run:
/home/youruser/linux-arm64/,whoamiyoucan
simply followCreate the
instructionsservicebelow,filebutOpen
overwriteyouruser` with a real username in your OSCreate a systemdthe service filesudointouchnano:/etc/systemd/system/vrsx.serviceCopy and paste the service configuration using for example nano (sudo nano /etc/systemd/system/vrsx.service:
Paste the configuration below:
[Unit] Description=VRSX After=network.target [Service] Type=simple User=youruser WorkingDirectory=/home/youruser/linux-arm64## change to linux-x64 if you are on Intel/AMD machineExecStart=/home/youruser/linux-arm64/VRSX --headless## change to linux-x64 if you are on Intel/AMD machine # If your system is RHEL-based, for example Rocky Linux/CentOS, please remove ExecStart line above and uncomment the line below to avoid issues with SELinux: # ExecStart=/bin/bash -c '/opt/linux-x64/VRSX --headless'Restart=on-failure RestartSec=5 [Install] WantedBy=multi-user.targetOnceBeforedone,saving,clickmake sure you changed:youruserto your real Linux username.
If you are using the x64 version, also change:
linux-arm64to:
linux-x64Save and exit nano:
Ctrl+O(save),Enter Ctrl+X(exit)WARNING: Old Linux
jokejoke::If you want to create a strong admin password, tryto editediting this fileusingwithvi, LOL..Make sure you haveoverwrittenyouruserwith your usernameEnable and
removedstartallthecommentsservice(after ##)Reload
systemdsystemd:using commandsudo systemctl daemon-reloadStartEnable VRSX at boot and
enablestartVRSitXnow:service using commandsudo systemctl enable vrsx --nowVisitCheck service status:
sudo systemctl status vrsxIf everything looks good, open VRSX in your
VRSbrowser:X instance on porthttp://IP.OF.YOUR.MACHINE:8085(i.e.Example:
http://192.168.100.100:8085)8085andactivateActivate
itVRSX using thelicencelicense keygivenavailableinunder"MYtheAccount"“My Account” section in ADS-B.ProRadarViewRadarView.
RHEL, Rocky Linux, CentOS and SELinux notes
On some RHEL-based systems, SELinux may complain harder than a Windows admin forced to use a terminal.
If the regular
ExecStartline does not work, you can try wrapping the command in Bash.Replace this line:
ExecStart=/home/youruser/linux-arm64/VRSX --headlesswith:
ExecStart=/bin/bash -c '/home/youruser/linux-arm64/VRSX --headless'Then reload and restart the service:
sudo systemctl daemon-reload sudo systemctl restart vrsxCheck the logs if something still refuses to cooperate:
journalctl -u vrsx -eOr follow logs live:
journalctl -u vrsx -f
Useful service commands
Start VRSX:
sudo systemctl start vrsxStop VRSX:
sudo systemctl stop vrsxRestart VRSX:
sudo systemctl restart vrsxDisable VRSX from starting at boot:
sudo systemctl disable vrsxView logs:
journalctl -u vrsx -eFollow logs live:
journalctl -u vrsx -f-
Before