Caddy

From caddyserver.com:

Caddy 2 is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go

The configurations here assume you have installed Caddy via package manager, and are using systemd to run Caddy.

---

Here is a dead-simple way to have Caddy act as a reverse-proxy in front of NodeBB:

caddy reverse_proxy --from example.org --to localhost:4567

That was fast! – but we'll probably want something more permanent.

---

To use a Caddyfile instead (which you probably do), here is that same setup:

example.org
reverse_proxy localhost:4567

Save those two lines into /etc/caddy/Caddyfile and reload Caddy (systemctl reload caddy). This configuration will work even if you have configured NodeBB's url to contain a subfolder.

---

If you want a more robust setup with compression and direct file-serving for built assets (as mentioned in Scaling NodeBB):

example.org {
    encode zstd gzip

    handle_path /assets/* {
        root * /path/to/nodebb
        try_files /build/public/{path} /public/{path}
        file_server
    }

    handle {
        reverse_proxy localhost:4567
    }
}

Neat!

In this example, you'll need to modify /path/to/nodebb to point to your NodeBB installation. If you are configuring a subfolder install, prepend the folder name to /assets (e.g. /forum/assets/*).