- With the latest release from 2020-05-27 the operating system was renamed from Raspbian to Raspberry Pi OS and its image names are changed from e.g. 2020-02-13-raspbian-buster.zip to 2020-05-27-raspios-buster-armhf.zip, with the postfix -armhf. This implies that there could also be a version with -arm64.
- Agent DVR is a new advanced video surveillance platform for Windows, Mac OS, Linux, Raspberry Pi and Docker.Agent has a unified user interface that runs on all modern computers, mobile devices and even Virtual Reality.
Download Agent DVR v3.2.5.0
Agent DVR is a new advanced video surveillance platform for Windows, Mac OS, Linux, Raspberry Pi and Docker. Agent has a unified user interface that runs on all modern computers, mobile devices and even Virtual Reality. Agent DVR supports remote access from anywhere with no port forwarding required.*
Available languages include: English, Nederlands, Deutsch, Español, Française, Italiano, 中文, 繁体中文, Português, Русский, Čeština and Polskie
To install run the setup utility which will check the dependencies, download the application and install the service and a tray helper app that discovers and monitors Agent DVR network connections.
Agent for Windows runs on Windows 7 SP1+. Requires the .net framework v4.7+.
To run on Windows Server you will need to enable Windows Media Foundation. For server 2012, install that from here.
If you need to install Agent on a PC without an internet connection you can download the application files manually here: 32 bit, 64 bit
- Download and install the dotnet core runtime for Mac OS
- Install homebrew: https://brew.sh/
- Open a terminal and run:
brew install ffmpeg - Run
dotnet Agent.dllin a terminal window in the Agent folder. - Open a web browser at http://localhost:8090 to start configuring Agent. If port 8090 isn't working check the terminal output for the port Agent is running on.
Agent for Linux has been tested on Ubuntu 18.04, 19.10, Debian 10 and Linux Mint 19.3. Other distributions may require additional dependencies. Use the docker option if you have problems installing.
Dependencies:
- Agent currently uses the .Net core 3.1 runtime which can be installed by running:
sudo apt-get update && sudo apt-get install -y apt-transport-https && sudo apt-get update && sudo apt-get install -y aspnetcore-runtime-3.1 - More information (you may need to add package references): https://dotnet.microsoft.com/download/dotnet-core/3.1
#openHABian - Hassle-free openHAB Setup. The Raspberry Pi is quite a famous platform for openHAB. However, setting up a fully working Linux system with all recommended packages and openHAB recommendations is a boring task, takes a lot of time and Linux newcomers are challenged in a number of ways although all they want is to run openHAB and not some server.
You also need to install FFmpeg v4.x - one way of getting this via the terminal in Linux is:
sudo apt-get updatesudo add-apt-repository ppa:jonathonf/ffmpeg-4ORsudo add-apt-repository ppa:savoury1/ffmpeg4for Xenial and Focalsudo apt-get update && sudo apt-get install -y ffmpeg
Important: Don't use the default ffmpeg package for your distro as it doesn't include specific libraries that Agent needs
Other libraries Agent may need depending on your Linux distro:
sudo apt-get install -y libtbb-dev libc6-dev gss-ntlmssp
For Debian 10 (and possibly other distros):
sudo wget http://security.ubuntu.com/ubuntu/pool/main/libj/libjpeg-turbo/libjpeg-turbo8_1.5.2-0ubuntu5.18.04.4_amd64.debsudo wget http://fr.archive.ubuntu.com/ubuntu/pool/main/libj/libjpeg8-empty/libjpeg8_8c-2ubuntu8_amd64.debsudo apt install multiarch-supportsudo dpkg -i libjpeg-turbo8_1.5.2-0ubuntu5.18.04.4_amd64.debsudo dpkg -i libjpeg8_8c-2ubuntu8_amd64.deb
For VLC support (optional):
sudo apt-get install -y libvlc-dev vlc libx11-dev
Download Agent:
- Unzip the Agent DVR files, open a terminal and run:
dotnet Agent.dllin the Agent folder. - Open a web browser at http://localhost:8090 to start configuring Agent. If port 8090 isn't working check the terminal output for the port Agent is running on.
Instructions here are for Raspbian. If you have a different Linux ARM install you may need to follow the instructions on the Linux tab but use the Agent download links below.
- Download the dotnet core runtime for Arm 32 or Arm 64
- Setup the dotnet runtime (use aspnetcore-runtime-3.1.11-linux-arm64.tar.gz for 64 bit):
sudo mkdir /usr/share/dotnet/
export PATH=$PATH:/usr/share/dotnet/dotnet
export DOTNET_ROOT=/usr/share/dotnet/dotnet
sudo tar zxf aspnetcore-runtime-3.1.11-linux-arm.tar.gz -C /usr/share/dotnet/
If your OS doesn't already have a shared FFmpeg build installed (64 bit Buster on the Pi comes with compatible FFmpeg):
- Setup Snap (will reboot):
sudo apt update
sudo apt install snapd
sudo reboot - Install Snap Core:
sudo snap install core - Install FFmpeg (v4):
snap install ffmpeg
Other libraries Agent may need depending on your distro:
sudo apt-get install -y libtbb-dev libc6-dev gss-ntlmssp libatlas
For VLC support (optional):
sudo apt-get install -y libvlc-dev vlc libx11-dev
Download Agent:
- Download the Agent DVR ▼ Arm 32 bit or ▼ Arm 64 bit files
- Unzip the Agent DVR files, open a terminal and run:
dotnet Agent.dllin the Agent folder. - Open a web browser at http://localhost:8090 to start configuring Agent. If port 8090 isn't working check the terminal output for the port Agent is running on.
A Docker image of Agent DVR will install Agent DVR on a virtual Linux image on any supported operating system. Please see the docker file for options.
Important: The docker version of Agent includes a TURN server to work around port access limitations on Docker. If Docker isn't running in Host mode (which is only available on linux hosts) then you will need to access the UI of Agent by http://IPADDRESS:8090 instead of http://localhost:8090 (where IPADDRESS is the LAN IP address of your host computer).
To install Agent under docker you can call (for example):
docker run -it -p 8090:8090 -p 3478:3478/udp -p 50000-50010:50000-50010/udp --name agentdvr doitandbedone/ispyagentdvr:latestTo run Agent if it's already installed:
docker start agentdvr
If you have downloaded Agent DVR to a VPS or a PC with no graphical UI you can setup Agent for remote access by calling 'Agent register' on Windows or 'dotnet Agent.dll register' on OSX or Linux. This will give you a claim code you can use to access Agent remotely.
or.. Download iSpy v7.2.1.0
iSpy is our original open source video surveillance project for Windows. iSpy runs on Windows 7 SP1 and above. iSpy requires the .net framework v4.5+. To run on windows server 2012 you will need to install media foundation.
Click to download the Windows iSpy installer. We recommend Agent DVR for new installations.
*Remote access and some cloud based features are a subscription service (pricing) . This funds hosting, support and development.
Whilst our software downloads would you do us a quick favor and let other people know about it? It'd be greatly appreciated!
Table of Contents
- Alternate installation methods
- Certbot-Auto
Certbot is meant to be run directly on a web server, normally by a system administrator. In most cases, running Certbot on your personal computer is not a useful option. The instructions below relate to installing and running Certbot on a server.
System administrators can use Certbot directly to request certificates; they should not allow unprivileged users to run arbitrary Certbot commands as root, because Certbot allows its user to specify arbitrary file locations and run arbitrary scripts.
Certbot is packaged for many common operating systems and web servers. Check whethercertbot (or letsencrypt) is packaged for your web server’s OS by visitingcertbot.eff.org, where you will also find the correct installation instructions foryour system.
Note
Unless you have very specific requirements, we kindly suggest that you use the installation instructions for your system found at certbot.eff.org.
Certbot currently requires Python 2.7 or 3.6+ running on a UNIX-like operatingsystem. By default, it requires root access in order to write to/etc/letsencrypt, /var/log/letsencrypt, /var/lib/letsencrypt; tobind to port 80 (if you use the standalone plugin) and to read andmodify webserver configurations (if you use the apache or nginxplugins). If none of these apply to you, it is theoretically possible to runwithout root privileges, but for most users who want to avoid running an ACMEclient as root, either letsencrypt-nosudo or simp_le are more appropriate choices.
The Apache plugin currently requires an OS with augeas version 1.0; currently itsupportsmodern OSes based on Debian, Ubuntu, Fedora, SUSE, Gentoo and Darwin.
If you are offline or your operating system doesn’t provide a package, you can usean alternate method for installing certbot.
Most modern Linux distributions (basically any that use systemd) can installCertbot packaged as a snap. Snaps are available for x86_64, ARMv7 and ARMv8architectures. The Certbot snap provides an easy way to ensure you have thelatest version of Certbot with features like automated certificate renewalpreconfigured.
You can find instructions for installing the Certbot snap athttps://certbot.eff.org/instructions by selecting your server software and thenchoosing “snapd” in the “System” dropdown menu. (You should select “snapd”regardless of your operating system, as our instructions are the same acrossall systems.)
Docker is an amazingly simple and quick way to obtain acertificate. However, this mode of operation is unable to installcertificates or configure your webserver, because our installerplugins cannot reach your webserver from inside the Docker container.
Most users should use the instructions at certbot.eff.org. You should only useDocker if you are sure you know what you are doing and have a good reason to doso.
You should definitely read the Where are my certificates? section, in order toknow how to manage the certsmanually. Our ciphersuites pageprovides some information about recommended ciphersuites. If none ofthese make much sense to you, you should definitely use the installation methodrecommended for your system at certbot.eff.org, which enables you to useinstaller plugins that cover both of those hard topics.
If you’re still not convinced and have decided to use this method, fromthe server that the domain you’re requesting a certficate for resolvesto, install Docker, then issue a command like the one found below. Ifyou are using Certbot with the Standalone plugin, you will needto make the port it uses accessible from outside of the container byincluding something like -p80:80 or -p443:443 on the commandline before certbot/certbot.
Docker Raspbian Buster Command
Running Certbot with the certonly command will obtain a certificate and place it in the directory/etc/letsencrypt/live on your system. Because Certonly cannot install the certificate fromwithin Docker, you must install the certificate manually according to the procedurerecommended by the provider of your webserver.
There are also Docker images for each of Certbot’s DNS plugins availableat https://hub.docker.com/u/certbot which automate doing domainvalidation over DNS for popular providers. To use one, just replacecertbot/certbot in the command above with the name of the image youwant to use. For example, to use Certbot’s plugin for Amazon Route 53,you’d use certbot/dns-route53. You may also need to add flags toCertbot and/or mount additional directories to provide access to yourDNS API credentials as specified in the DNS plugin documentation.
For more information about the layoutof the /etc/letsencrypt directory, see Where are my certificates?.
Warning
While the Certbot team tries to keep the Certbot packages offeredby various operating systems working in the most basic sense, due todistribution policies and/or the limited resources of distributionmaintainers, Certbot OS packages often have problems that other distributionmechanisms do not. The packages are often old resulting in a lack of bugfixes and features and a worse TLS configuration than is generated by newerversions of Certbot. They also may not configure certificate renewal for youor have all of Certbot’s plugins available. For reasons like these, werecommend most users follow the instructions athttps://certbot.eff.org/instructions and OS packages are only documentedhere as an alternative.
Arch Linux
Debian
If you run Debian Buster or Debian testing/Sid, you can easily install certbotpackages through commands like:
If you run Debian Stretch, we recommend you use the packages in Debianbackports repository. First you’ll have to follow the instructions athttps://backports.debian.org/Instructions/ to enable the Stretch backports repo,if you have not already done so. Then run:
In all of these cases, there also packages available to help Certbot integratewith Apache, nginx, or various DNS services. If you are using Apache or nginx,we strongly recommend that you install the python-certbot-apache orpython-certbot-nginx package so that Certbot can fully automate HTTPSconfiguration for your server. A full list of these packages can be foundthrough a command like:
They can be installed by running the same installation command above butreplacing certbot with the name of the desired package.
Ubuntu
If you run Ubuntu, certbot can be installed using:
Optionally to install the Certbot Apache plugin, you can use:
Fedora
FreeBSD
- Port:
cd/usr/ports/security/py-certbot&&makeinstallclean - Package:
pkginstallpy27-certbot
Gentoo
The official Certbot client is available in Gentoo Portage. From theofficial Certbot plugins, three of them are also available in Portage.They need to be installed separately if you require their functionality.
Note
The app-crypt/certbot-dns-nsone package has a differentmaintainer than the other packages and can lag behind in version.
NetBSD
Docker Debian Buster Python
- Build from source:
cd/usr/pkgsrc/security/py-certbot&&makeinstallclean - Install pre-compiled package:
pkg_addpy27-certbot
OpenBSD
- Port:
cd/usr/ports/security/letsencrypt/client&&makeinstallclean - Package:
pkg_addletsencrypt
Other Operating Systems
OS packaging is an ongoing effort. If you’d like to packageCertbot for your distribution of choice please have alook at the Packaging Guide.
We used to have a shell script named certbot-auto to help people installCertbot on UNIX operating systems, however, this script is no longer supported.If you want to uninstall certbot-auto, you can follow our instructionshere.
When using certbot-auto on a low memory system such as VPS with less than512MB of RAM, the required dependencies of Certbot may fail to build. This canbe identified if the pip outputs contains something like internalcompilererror:Killed(programcc1). You can workaround this restriction by creatinga temporary swapfile:
Disable and remove the swapfile once the virtual environment is constructed:
Installation from source is only supported for developers and thewhole process is described in the Developer Guide.
Warning
Please do not use pythoncertbot/setup.pyinstall, pythonpipinstallcertbot, or easy_installcertbot. Please do not attempt theinstallation commands as superuser/root and/or without virtual environment,e.g. sudopythoncertbot/setup.pyinstall, sudopipinstall, sudo./venv/bin/.... These modes of operation might corrupt your operatingsystem and are not supported by the Certbot team!