DOWNLOAD / RELEASE

Downloads and releases

Pick the right build, check the prerequisites and get the server running. This page covers every distribution form, the current release and what to keep when upgrading.

CURRENT RELEASE See the release page Release date on the release page

All releases Changelog Gitee

Artifacts files listed on the release pages

fast-https-<version>-windows-amd64-setup.exeWindows · x64 · desktop clientGet

fast-https-<version>-windows-arm64-setup.exeWindows · ARM64 · desktop clientGet

fast-https_Windows_x86_64.zipWindows · x64 · portable, no GUIGet

fast-https_Linux_x86_64.tar.gzLinux · x86_64 · serviceGet

Exact filenames and checksums are published on the release page.

Which build should I get?

Same server, four ways to ship it. They differ in the desktop client, whether anything is installed, and how the process stays running.

FORM	BEST FOR	CONTAINS	WATCH OUT FOR
Windows installer	You want a tray icon and a graphical client	setup.exe, desktop client, shortcuts, uninstaller	Not code-signed, so browsers warn about an uncommon download — choose Keep	Get
Windows portable zip	No install, unpack and run, quick tests	fast-https.exe plus config, httpdoc and logs folders	No monitor.exe and no GUI; start runs in the foreground, closing the window stops the server	Get
Linux tarball	Long-running servers managed by systemd	fast-https binary, default config, sample site	Needs free ports 80/443 and root; config paths are relative to the unpack directory	Get
Docker image	Container deployments	alpine, ubuntu and centos7 tags	A mount replaces the folder inside the container, so host folders must not be empty	Guide
Build from source	Contributing or reproducing a build	Go backend and the management console frontend	Requires Go 1.21+, Node.js 18+ and Git	Guide

Before you install

Ports 80 and 443 must be free; if not, change listen to high ports such as 8080 / 8443
Use a writable path without spaces or non-ASCII characters
Binding 80/443 or installing a service needs administrator / root rights
The first start generates a self-signed certificate into config/cert/, so a browser warning is expected; use acme for a trusted certificate
The archive has config/fast-https.json for global settings and conf.d/ for one file per site — the defaults already run

Up in three steps

Windows (portable zip)

CMD.\fast-https.exe start

Unpack into a writable folder
Run the command above from that folder
Open the address from listen in config/conf.d/default.json — the welcome page means it works

Linux (tarball)

SH./fast-https start

Unpack into a writable folder
Run the command above from that folder
Open the address from listen in config/conf.d/default.json — the welcome page means it works

On Windows, start stays in the foreground: keep the window open, stop with Ctrl+C or fast-https.exe stop. On Linux it daemonises by itself.

Verify the download

Compare the SHA256 of the file you downloaded with the checksum published on the release page.

WINcertutil -hashfile fast-https_Windows_x86_64.zip SHA256

UNIXsha256sum fast-https_Linux_x86_64.tar.gz

Upgrading and known issues

Keep your configuration and certificates when replacing the binary. Changing config does not require reinstalling.

Keep config/, conf.d/, cert/, httpdoc/ and logs/; replace only the executable
Run fast-https reload after editing config; unchanged ports only swap the configuration snapshot, in-flight connections keep serving
Read the changelog before a major upgrade in case config fields changed

Known issues

v1.6.1 portable zip no longer contains monitor.exe — older tutorials telling you to double-click it are obsolete
The installer is not code-signed, so the first download triggers a browser or SmartScreen warning
The self-signed certificate is not trusted by browsers; use acme for public sites