#### Version 2.9.91 This new version includes our fresh new **Streaming Engine** web interface which makes the **XProtect Management Client Plugin** obsolete (except for choosing which cameras are allowed over `RTSP`). We are currently conducting tests on version 2.9.91, and while advanced features such as SRT and ONVIF camera support may experience occasional issues, core functionalities including RTSP, RTSPS, and Load Balancing are fully stable and reliable. This version will be publicly available for download on our website starting next week (**27/06/2025**). We have been very busy implementing all this, we hope you will enjoy all the new features! # Install #### .NET Before you install anything, make sure to install the latest version of **ASP.NET9** (`dotnet-hosting-9.0.4-win.exe` included in the **Streaming Engine** installer zip folder): Otherwise download: https://builds.dotnet.microsoft.com/dotnet/aspnetcore/Runtime/9.0.4/dotnet-hosting-9.0.4-win.exe  #### Load Balancer Run `ORBNET Load Balancer Service Setup v2.9.91.msi` `Next` -> [I Agree] `Next` -> `Next` -> `Next` -> `Close` ![[z_img/da52256896f9e079a26ad6ecf0073d15_MD5.jpeg]] # Web Interface **For login to the new webpages, the default URLs are:** Streaming Engine: [https://127.0.0.1:45336/login](https://127.0.0.1:45336/login) Load Balancer: [https://localhost:45338/login](https://localhost:45338/login) > [!info]- Default Credentials > **Username:** `admin` > **Password:** `admin123` You will land on a login page before being granted access. Example: `https://127.0.0.1:45336/login` After a while, the security token will expire and you must login again with the `/login` in the URL.  Our **Streaming Engine** has many new features now available from this web interface.:  **Added features:** -Secured all Streaming Engine webpage interfaces with SSL. -Support for multiple **Load Balancer** addresses (add one address per line and the **Streaming Engines**. will send load balancing information to each one). -Support for **RTSPS URL**. Use the checkbox and the **Load Balancer** will redirect to the **RTSPS URL**.  You may need to specify the `External RTSP URL` for the load balancer because sometimes the hostname won’t resolve properly and `RTSPS` URL won’t work. Instead, please manually add the `IP address` here for best stability. The IP address must be the local IP of the **Streaming Engine**, and the port must be the RTSP Server SSL port.  - **RTSPS self-signed certificates** are automatically installed in the `Local Computer` -> `Personal` -> `Certificates` store when you run the installers. The self-signed certificates are used to encrypt the **RTSPS** streams with **SSL sha256, RSA (2048 Bits)**.  If you want to use your own certificates, simply change the WebStreaming certificate thumbprint in the Streaming Engine config:  And you can also modify the `RTSPStreamingCertificateThumbprint` in the load balancer config:  You will need to allow `Network Service` to access the private key of the certificates. Please follow this procedure for both certificates contained in the `Local Computer` -> `Personal` -> `Certificates` store. You can Identify them using the “Friendly Name” column with NETCore and Load Balancer as seen below:  # Video Streaming Tests **VLC Player** does not work with Secure RTSP, but you can use **FFPlay** to get it working. It also handles 302 redirects. 1. Download `FFMPEG` 2. Install `ffmpeg` - [https://www.gyan.dev/ffmpeg/builds/](https://www.gyan.dev/ffmpeg/builds/) - Release builds -> download “ffmpeg-release-full.7z” - Extract it to “C:\ffmpeg” 3. Run Windows Command Prompt, ```shell hl:2 cd c:\ffmpeg ffplay.exe rtsps://127.0.0.1:755/<cameraGuid> ``` Update the <==cameraGuid==> in the above and it will show the redirect URL and open the stream to view.