Free APT repository  ·  Open-source project  ·  No registration

NGINX and Angie packages for Debian and Ubuntu

40+ source packages, with HTTP/3, mail services and web application firewall tools ready to install. This free APT repository for NGINX and Angie gives Debian and Ubuntu administrators builds with features and modules beyond the standard distribution packages.

Built for the servers we operate. Available without registration, with GPG-signed repository metadata and documented APT pinning.

# Installs GPG key, APT source and pinning in one step
$ wget https://raw.githubusercontent.com/eilandert/deb.myguard.nl/main/myguard.deb
$ dpkg -i myguard.deb
$ apt-get update && apt-get install nginx
Works on Debian 12/13 and Ubuntu 22.04/24.04/26.04 on amd64 + arm64, Debian 11 on amd64  ·  Manual setup →  ·  How the repository is laid out
100+
NGINX & Angie modules
40+
Source packages across the repository
60+
Deep-dive articles
GPG
Signed repository metadata

An APT repository for NGINX, Angie and the rest of your stack

Choose a web server, add the modules your application needs, and manage updates through APT. The repository also covers the mail and security services around it, so you can follow one set of installation guides across the stack.

// performance

HTTP/3 and modern TLS

NGINX and Angie use openssl-nginx, a dedicated OpenSSL 4.0 build with QUIC support. NGINX also uses zlib-ng. The HTTP/3 setup guide covers the configuration and network checks needed after installation.

// features

Modules you can select

Add Brotli compression, ModSecurity, Lua modules or njs with QuickJS as your workload needs them. The module catalogue explains what each module does; you don’t have to enable everything just because it is available.

// freshness

Upstream releases, packaged for APT

We package upstream releases for Debian and Ubuntu rather than waiting for the distribution’s next major release. Check the changelog for actual updates and the package list for availability. Review changes before upgrading a production service.

// security

Security tools with setup guides

Build a WAF with ModSecurity and the OWASP Core Rule Set, add Snuffleupagus hardening for PHP-FPM, or use hardened OpenSSH on Debian 13 and Ubuntu 26.04. Each tool has its own configuration and compatibility requirements.

// containers

Containers from the same packages

The NGINX and Angie images are rebuilt nightly with modules compiled in. Use the Kubernetes guide for deployment details, or install the packages directly when you manage the host yourself.

// trust

Signed metadata and clear provenance

APT verifies signed repository metadata and checks package hashes against that metadata. The signed-by setting scopes the repository key to its source entry. Read the installation and pinning guide before replacing distribution packages. A signature verifies origin and integrity, not suitability for your server.

Articles and practical server guides

The articles explain how the packages fit together, what to configure after installation and how to investigate failures. Start with the task you need to finish. Each guide links to the relevant tools and settings.

// web servers

Choose and configure NGINX or Angie

Compare the servers, set up a reverse proxy and work through TLS and HTTP/3 configuration. These guides explain the settings behind the install commands.

Angie: features and migration
TLS configuration for NGINX and Angie

// mail and filtering

Build a mail stack you can maintain

Set up a mail server with Postfix and Dovecot and filter spam. Understand where Rspamd and attachment scanning fit into the process and which part to look at when mail delivery fails.

Postfix and Dovecot setup
How Rspamd filters spam

// security and operations

Harden services and diagnose problems

Configure a WAF and review container privileges. The guides explain how these controls fit into a deployment and where their limits are, with configuration details you can apply to your own setup.

ModSecurity and OWASP CRS setup
Docker hardening for self-hosters

Featured packages

Browse the main web, mail and security packages below. The full package list is the reference for available packages; the distribution notes explain release and architecture coverage.

Mainline release with HTTP/3 and QUIC; Brotli, ModSecurity and 100+ other modules come as separate packages
HTTP/3
Drop-in NGINX replacement with native ACME (no Certbot) and extended metrics
HTTP/3 ACME
Current Apache HTTP Server, built with Brotli compression
OpenSSL 4.0 build with QUIC support, used by NGINX and Angie for HTTP/3
QUIC
Postfix 3.11 with modern TLS
Mail
Current Dovecot IMAP/POP3 server with the Sieve plugin
Mail
Fast spam filtering for Postfix and Dovecot
Mail
ModSecurity v3 WAF library; with modsecurity-crs it runs the OWASP Core Rule Set in NGINX and Angie
WAF
Google’s Brotli library, needed by the NGINX Brotli module
Compression
BSD-licensed Redis fork with a tight systemd sandbox and an AppArmor profile
Cache
Hardened OpenSSH with post-quantum key exchange (Debian 13 and Ubuntu 26.04)
Security
Runtime hardening for PHP-FPM: blocks dangerous functions and common exploit paths
Security
FIDO2 library for hardware keys (YubiKey) in OpenSSH and other tools
Security
Compiler cache for faster repeated builds
Dev

→ NGINX modules overview  ·  Angie modules overview  ·  Lua modules  ·  Full packages page  ·  Source on GitHub

NGINX & Angie modules we wrote ourselves

We develop and maintain these NGINX and Angie modules alongside the repository. They cover compression, caching, certificate management and request filtering. Each has a guide and source repository, so you can check its behaviour before adding it to a server.

// compression

zstd-nginx-module

Our fork of the Zstandard compression module, with several upstream bugs fixed and clean builds against current NGINX and Angie. What we fixed · What zstd is · GitHub

// abuse

error-abuse

Bans clients that flood you with 403, 404 or 5xx responses, fail2ban-style but inside NGINX. Sliding-window counters in shared memory, with optional cluster-wide bans through Redis or Valkey. Guide · GitHub

// cache

cache-turbo

A page cache inside NGINX itself, so you don’t need Varnish or a second daemon. Stale-while-revalidate, L0, L1 and L2 tiers and single-flight refresh. Guide · GitHub

// tls

autocert

Gets and renews TLS certificates over ACME from inside NGINX, so Certbot and its cron job can go. Guide · GitHub

// shield

http-shield

Blocks probes for ancient exploits cheaply, without running a full WAF. Guide · GitHub

// minify

strip-filter

Minifies CSS and JavaScript as NGINX serves it, for apps that ship unminified assets. Guide · GitHub

Writing a module of your own? Start from nginx-skeleton-module, a template with working CI, and catch leaks with nginx-test-harness. → All NGINX modules  ·  All Angie modules  ·  Every repo on GitHub

ModSecurity & the OWASP Core Rule Set

A complete WAF stack for NGINX and Angie: the ModSecurity v3 engine, the OWASP CRS, and our own CRS plugins for apps we self-host. The plugins also run on Apache with mod_security2. If you’d rather not use ModSecurity, Coraza runs the same CRS rules.

// wordpress

WordPress hardening CRS plugin

Over 100 rules tuned for WordPress: typed-parameter SQLi blocking, rate limiting, GeoIP and an XML-RPC lockdown, all enforced before PHP starts. Guide · GitHub

// vaultwarden

vaultwarden-crs-plugin

Rules and exclusions that let the WAF sit in front of self-hosted Vaultwarden without blocking normal client traffic. GitHub

// vimbadmin

vimbadmin-crs-plugin

Rules and exclusions for the ViMbAdmin mail admin panel, so the WAF protects it without breaking its JSON-RPC API. GitHub

→ All our CRS plugins  ·  ModSecurity setup on Debian and Ubuntu  ·  Defending against AI exploit scanners  ·  JA3/JA4 TLS fingerprinting  ·  The BREACH attack

Mail security, container images and open-source tools

The repository is part of a wider set of tools we use to run web and mail infrastructure. Explore the projects below, or use the project directory to find source repositories and images.

// mail security

Mailstrix

Mailstrix unpacks mail attachments and scans them with YARA rules. It supports integrations with Rspamd, SpamAssassin, Dovecot Sieve and ICAP. The Mailstrix guide explains the scanning path; the Olefy guide covers Office macro scanning.

// containers

Docker images

Use NGINX and Angie images for container deployments, with separate images for Roundcube webmail and PHP and WordPress hosting. Check each image’s documented services, volumes and update procedure before deployment.

// source

github.com/myguard-labs

Find the code in the myguard-labs GitHub organisation. Project guides link to their repositories for source, configuration examples and issue reporting. The repository and image directory helps you find the right place to report a problem.

Which packages should you start with?

Choose the service you want to run first, then install the modules and security controls it requires. Installing packages is the start of configuring your system, not a finished production deployment.

A web server or reverse proxy

Start with nginx or angie. Angie includes native ACME certificate management; NGINX has a broad module ecosystem. Read the Angie migration guide before switching an existing installation. Add compression, caching or a WAF when you know which traffic and applications they will handle.

A mail server

Postfix is a mail transfer agent, Dovecot provides mailbox access and Sieve filtering and rspamd-git provides spam filtering. The mail server setup guide puts them all together. Plan DNS, certificates and authentication as part of the deployment.

A smaller self-hosted service

Install the packages your application needs rather than the whole catalogue. The nginx-minimal guide describes a smaller web server build, and the Vaultwarden guide shows how to run a self-hosted application behind a reverse proxy.

Built for the infrastructure we run

The repository began with packages we needed for our own web and mail servers. Maintaining the builds made it possible to publish the packages, then document the configuration around them. When an upstream module needed fixes, we maintained a fork; when a feature was missing, we developed a module. The zstd module history is one example.

You can use the repository without registration. The setup guide documents the key, source entry and APT pinning, while the changelog records package updates. If you maintain your own builds, the guides to hosting an APT repository with aptly and speeding up Debian package builds explain that part of the work.

Supported distributions

Builds cover Debian 11, 12 and 13, and Ubuntu 22.04, 24.04 and 26.04. Availability depends on the package, release and architecture; check the package list before planning a migration.

Debian
Bullseye (11) Bookworm (12) Trixie (13)
Ubuntu
Jammy (22.04 LTS) Noble (24.04 LTS) Resolute (26.04)

Green = current/recommended. Builds cover amd64 (x86-64) and arm64 (aarch64); Debian 11 gets a smaller set, with NGINX, Angie, Postfix and Dovecot on amd64 only. Curious about the next Debian release? Here’s what to expect from Debian 14 (Forky).

Quick start

Add the repository, update APT’s package index, then install the service you need. Run package-management commands with root privileges. On an existing server, take a configuration backup and review APT’s proposed changes before confirming an upgrade.

$ wget https://raw.githubusercontent.com/eilandert/deb.myguard.nl/main/myguard.deb
$ dpkg -i myguard.deb
$ apt-get update
# Web server with HTTP/3
$ apt-get install nginx
 
# NGINX alternative with built-in ACME/Let’s Encrypt
$ apt-get install angie
 
# Mail stack
$ apt-get install postfix dovecot-core rspamd-git
 
# WAF for NGINX
$ apt-get install libnginx-mod-http-modsecurity libmodsecurity3 modsecurity-crs

Need manual setup or APT pinning? Use the full setup guide. Moving from nginx-full or nginx-light? Read the package migration guide before changing variants.

Before upgrading a production server

Check the changelog and the guide for the service you are upgrading. Review package replacements, module compatibility and local configuration changes. Keep a tested rollback path and validate the service configuration before restarting it. APT pinning controls which repository wins; it doesn’t test an application’s behaviour for you.

Need a manual source entry, key verification or pinning details? Use the full installation guide. For configuration examples and troubleshooting, go to the articles and server guides.