With this setup, it’s a fairly generic configuration with the exception of “Use X-Forwarded-For Headers” being checked. nginx will be handling all of the HTTPS/encryption from the net to the Blue Iris web server – mostly.Ĭlick the “Advanced…” button at the bottom of the Web Server tab. If your WAN IP was to be 12.34.56.78, you would input that to the Remote input field.Įnsure stunnel is unchecked. Your “Remote, External access” needs to equal the IP address of your WAN IPv4 address. This is a subdomain, not a folder we’ll be configuring. “Virtual” has to be just a forward slash /. You will need to input the machines LAN IPv4 address into the “Local, internal access” input. Otherwise, we run into some “fun” issues later on with security and general access problems.Įnsure your options look something similar to the above image. On Blue Iris’s application, we need to ensure the server accepts some variables from nginx along with setting a logical configuration.
#BLUE IRIS SERVER INSTALL#
The Blue Iris install does not use stunnel.nginx will internally route (user doesn’t see this happen!) the HTTPS request (be it lan or wan) to a HTTP request within the lan to the Blue Iris server.You’re running Blue Iris version 5 or newer.You are configuring this as a sub-domain (e.g.You have a wildcard based SSL certificate created and in-use/active for the reverse proxy access domain name.In this blog, will lay out the process to ensure nginx and BI plays (mostly) nice with Blue Iris web server. It sports a trendy web UI for viewing of the cameras added to the Blue Iris application. Blue Iris… for the uninitialized is a CCTV viewing, recording, nearly-do-everything-CCTV application for analog, IP/digital, and usb based cameras.
0 kommentar(er)
