akama-aka / WebProxy_f

An HTTP(S) reverse proxy server with web-based configuration.

WebProxy

An HTTP(S) reverse proxy server with web-based configuration. WebProxy is an easier alternative to more advanced command-line and config-file-driven reverse proxies like nginx or traefik.

See the Admin Console Tour for more screenshots.

Features

• Web-based configuration GUI
• HTTP/1.1 protocol (HTTP 2.0 and newer are not supported at this time, as this is largely irrelevant for small-scale usage)
• Request routing based on hostname (one IP address, multiple web sites)
• Automatic certificates from LetsEncrypt (optional)
  • Usage of this feature indicates acceptance of LetsEncrypt's Terms of Service
  • Supported validation methods include HTTP-01, TLS-ALPN-01. WebProxy will automatically select between validation methods HTTP-01 or TLS-ALPN-01 with a preference for HTTP-01 if both ports are available.
  • HTTP-01 validation requires the domain to be reachable via the internet using HTTP on port 80.
  • TLS-ALPN-01 validation requires the domain to be reachable via the internet using HTTPS on port 443.
  • DNS-01 validation is also available, but requires you to use Cloudflare Registrar and provide a Cloudflare API Token. This validation method will work even if you can't accept inbound traffic on ports 80 or 443.
• WebSocket support
• TLS 1.2 support
• TLS 1.3 support on operating systems that provide it via the SslStream API (Windows 11, Server 2022, Ubuntu Server 22.04, and others).
• Middleware system to manipulate proxy requests or add usage constraints. Middlewares can be enabled individually for each proxied website. Available middleware types:
  • IPWhitelist - Provides IP whitelisting of client connections.
  • HttpDigestAuth - This middleware causes requests to require HTTP Digest Authentication.
  • RedirectHttpToHttps - Requests coming in using plain HTTP are redirected to HTTPS. Requires the Entrypoint to support both HTTP and HTTPS.
  • AddHttpHeaderToResponse - Adds a user-defined static HTTP header to proxied responses.
  • AddProxyServerTiming - Adds a Server-Timing HTTP header to proxied responses which includes timing details for the proxied connection. This information appears in a web browser's developer console when you inspect a network request's timing.
  • XForwardedFor - Adds an X-Forwarded-For header according to rules you specify.
  • XForwardedHost - Adds an X-Forwarded-Host header according to rules you specify.
  • XForwardedProto - Adds an X-Forwarded-Proto header according to rules you specify.
  • XRealIp - Adds an X-Real-Ip header according to rules you specify.
  • TrustedProxyIPRanges - Allows you to specify which client IP addresses are trusted to provide proxy-related headers such as X-Forwarded-For.

Installation

Installation is simple but different between Windows and Linux. Just follow the appropriate instructions for your platform below and make sure any TCP ports you want to use for incoming traffic are allowed by any applicable firewalls and routers.

Windows Installation

Download a Windows release from the Releases Section, extract to a location of your choice, and run WebProxy.exe.
Click "Install", then "Start".
Click the "Admin Console" button to open a panel containing the admin credentials and links to the Admin Console website.

To update, just download a new release, stop the service, overwrite it, and start the service again.

Linux Installation Script

The Linux release of WebProxy is primarly tested on Ubuntu Server 22.04, but should work on any operating system that supports the .NET 6.0 Runtime.

On supported operating systems, run these commands to download and start the installation script:

wget https://raw.githubusercontent.com/bp2008/WebProxy/master/WebProxy/webproxy_install.sh
chmod u+x webproxy_install.sh
./webproxy_install.sh

The installation script will ask if you wish to 1) Install/Update or 2) Uninstall. The installation procedure will take a few minutes the first time, as it must install .NET 6.0. Later install/update operations are completed in seconds. Once installed, WebProxy will start automatically as a background service.

Access the interactive command line interface by running WebProxy with the argument "cmd":

sudo /usr/bin/dotnet ~/webproxy/WebProxyLinux.dll cmd

(the above command assumes you installed in your home directory)

Within the interactive command line interface, use the command admin to see the URLs and credentials for the Admin Console website.

The command line interface offers service management commands for install, uninstall, start, stop, etc. If you prefer, you can manage the webproxy service directly via standard systemctl commands (the service name is webproxy).

Can't use the installation script?

If you have an operating system not supported by the installation script, you can manually install the .NET 6.0 Runtime, then download and extract the WebProxy Linux release of your choice from Github's Releases Section. Once extracted, access the interactive command line interface via sudo /usr/bin/dotnet ~/webproxy/WebProxyLinux.dll cmd. If your computer has systemd, you can use WebProxy's install and other related commands to manage the service. If you need to use a different service manager, you should have it set an environment variable INVOCATION_ID=1 to trick WebProxy into thinking it is being run by systemd, and then run it via this command: sudo /usr/bin/dotnet ~/webproxy/WebProxyLinux.dll svc.

Getting Started

To learn how to configure WebProxy, use the question mark button in the upper right of the admin console. This button toggles help text throughout the admin console.

If you haven't installed WebProxy yet, you can read about WebProxy's basic concepts here.

Building From Source

Requirements:

• Visual Studio 2022 or newer
• .NET 6.0 SDK
• BPUtil utility library source (frequently updated; not published on Nuget)
• Node.js (tested with version 18) to build the Admin Console website

WebProxy and BPUtil repositories must be downloaded/cloned separately. To avoid needing to repair Project references, it is recommended to place both repositories in the same parent directory, e.g.

• ~/Repos/bp2008/BPUtil/BPUtil.sln
• ~/Repos/bp2008/WebProxy/WebProxy.sln

To build WebProxy:

1. Go to ~/Repos/bp2008/WebProxy/WebProxy/WebProxy-Admin in a command line terminal and run npm install. This will download all JavaScript dependencies. This only needs to be done once initially, and then again after you modify dependencies in package.json.
2. In Visual Studio, Build > Build Solution.

Notes:

• Output will be in the bin/Debug or bin/Release folders.
  • The cross-platform build (WebProxyLinux) will be located in a subfolder called net6.0.
  • The Windows build (WebProxy) will be located in a subfolder called net6.0-windows.
• In order for WebProxyLinux's post-build event to complete successfully, it must be built last, after WebProxy has finished. This serial ordering was set up by right clicking the WebProxyLinux project in Solution Explorer and choosing Build Dependencies > Project Dependencies. In this dialog, WebProxy was selected as a dependency of WebProxyLinux.