(Version on .NET Core 3.1)
1. Install .NET Core
Installing .NET Core on your OS is quite simple, but different Linux distributions use their own package managers. Download (paste) the installation script for your distribution (package manager) and run it on your system.
Please note: you may specifically need to install the .NET Core 3.1 version, because "ProxyLite" was built for this platform.
2. Download / install "ProxyLite"
After installing .NET Core, download "ProxyLite". ProxyLite is provided in a ZIP archive, which will need to be unpacked on your system, or if the installation is done remotely, 2 files (which are in the archive) can, can be transferred through file managers like WinSCP/FileZilla, etc.
An example of downloading and unpacking "ProxyLite" on a remote system. You will need the wget and unzip packages installed.
After downloading and unpacking "ProxyLite", you can directly run it. You will need to pass the --userid argument to the process.
dotnet ProxyService.Core.dll --userid 200149
Instead of 200149, be sure to include your account number (ID)!
The account number can be found in your personal account.
Also note the following point
After launch, the application log will appear. If Connection established appears in the terminal - congratulations, you did everything right! :)
[root@gavrilov proxylite-app]# dotnet ProxyService.Core.dll --userid 200149
[ProxyService] [INFO]: ProxyLite Application, version build 188.8.131.52 /
Runned on Linux 4.18.0-305.3.1.el8.x86_64 #1 SMP Tue Jun 1 16:14:33 UTC 2021[ProxyService] [INFO]: Setted user id 200149[ProxyService] [INFO]: Application initialization started[ProxyService] [INFO]: Trying get proxy node for connection[ProxyService] [INFO]: Proxy node is tcp://172.17.0.3:51022/[ProxyService] [INFO]: Certificate subject is CN=ProxyLite ProxyService Server, L="NOVOSIBIRSK ", C=RU, Eemail@example.com [ProxyService] [INFO]: [ProxyThread] Connection established
The example above does not allow the application to run in the background. To fix this, you need to use the nohup or screen utilities. Recommended - nohup.
Launch example using nohup.
nohup dotnet ProxyService.Core.dll --userid USER_ID &
The nohup utility will allow an application to ignore the SIGUP signal that occurs when an attempt is made to close the terminal. The output (log) will be redirected to nohup.out. The sign will allow the application to continue running in the background.
An example of launching via screen. The package may need to be installed.
screen -S proxylite dotnet ProxyService.Core.dll --userid USER_ID
Restore running version
screen -r proxylite
Also, "ProxyLite" can be installed as a daemon (service) so that at system startup - "ProxyLite" will automatically start