Hello everyone.
The world has no shortage of ways to do HTTPS reverse proxying to add
So I built my own HTTPS reverse proxy application with a web-based administration console. I can't take away the need for familiarity with basic networking concepts (IP addresses, port numbers, URLs, etc), but I can certainly build an application where you don't need to dig into a configuration file to make it work.
WebProxy is its name.
Here, I will explain how WebProxy can be used to set up an HTTPS endpoint for Blue Iris.
Get the service running:
1. Download the latest Windows release from here and extract it somewhere on your Blue Iris server.
2. Run
3. Click the "Admin Console" button, then click the localhost:8080 link to open the admin console website.
4. Log in using the credentials from the Admin Console Login Credentials dialog.
5. There is a question mark button in the upper right of the Admin Console which toggles inline help text to help you learn WebProxy's configuration. Click it so it turns green.
Tell WebProxy what ports you want it to listen on:
6. On the
7. Check the
Tell WebProxy about Blue Iris's web server:
8. On the
9. Choose
10. Type a star
11. Type
Create a route between your new Entrypoint and Exitpoint:
12. On the
13. Choose
Save
14. Click the red
The
To see it work, try loading or use whatever domain name and port number you configured.
If you have any trouble, check the
The world has no shortage of ways to do HTTPS reverse proxying to add
https:// capability to web applications (like Blue Iris) that lack good support natively: stunnel, nginx, apache, traefik, haproxy, Cloudflare DNS proxy, and many more. Most of these do not have a user interface, so you are required to read lots of documentation and write configuration files by hand, and that has always frustrated me. These programs should be easier to use.So I built my own HTTPS reverse proxy application with a web-based administration console. I can't take away the need for familiarity with basic networking concepts (IP addresses, port numbers, URLs, etc), but I can certainly build an application where you don't need to dig into a configuration file to make it work.
WebProxy is its name.
Here, I will explain how WebProxy can be used to set up an HTTPS endpoint for Blue Iris.
Get the service running:
1. Download the latest Windows release from here and extract it somewhere on your Blue Iris server.
2. Run
WebProxy.exe, press Install Service, then press Start Service. Allow firewall access if prompted.3. Click the "Admin Console" button, then click the localhost:8080 link to open the admin console website.
4. Log in using the credentials from the Admin Console Login Credentials dialog.
5. There is a question mark button in the upper right of the Admin Console which toggles inline help text to help you learn WebProxy's configuration. Click it so it turns green.
Tell WebProxy what ports you want it to listen on:
6. On the
Entrypoints tab on the left, add a new Entrypoint and name it Standard Entrypoint. 7. Check the
HTTPS Port checkbox, and if you prefer, customize the port number.Tell WebProxy about Blue Iris's web server:
8. On the
Exitpoints tab, add a new Exitpoint and name it Blue Iris.9. Choose
Exitpoint Type: WebProxy10. Type a star
* in the Host Binding field to make it listen to all hosts. If you have a domain name already routed to the Blue Iris computer, you can enter that name here instead.11. Type
http://127.0.0.1:81 in the Destination Origin field, changing port number 81 to whatever port your Blue Iris web server listens on.Create a route between your new Entrypoint and Exitpoint:
12. On the
Routes tab, add a new Route.13. Choose
Standard Entrypoint in the first dropdown box and choose Blue Iris in the second dropdown box.Save
14. Click the red
Save Changes button in the top bar of the Admin Console, and your changes will be applied immediately.The
Dashboard tab shows your new proxy route in the Hosted URL Summary.To see it work, try loading or use whatever domain name and port number you configured.
If you have any trouble, check the
Log tab to make sure the ports got bound correctly and no other errors have occurred.
Last edited:
