nginx | 11/17/2023 | By Thijs Eilander

nginx-core, nginx-full, nginx-light Are Gone — Here’s What to Use Instead (2026)

One day you run apt upgrade and see it: a warning that nginx-core, nginx-full, or nginx-light is being removed. Or maybe you’re setting up a fresh server and can’t find them anywhere. What happened? Where did they go? Are you supposed to panic?

Short answer: Debian deprecated these package variants. Long answer: this is actually good news, because the replacements are genuinely better. Let me explain what happened and exactly what to do about it.

NGINX logo — nginx-core nginx-full nginx-light deprecated alternatives
nginx-core, nginx-full, and nginx-light are gone — here’s what to use instead

What Were nginx-core, nginx-full, and nginx-light Anyway?

Back in the day, Debian shipped three flavours of NGINX in its official repo:

  • nginx-light — the bare minimum: just HTTP serving, no extras
  • nginx-core — a middle ground with a handful of common modules
  • nginx-full — the kitchen-sink version with as many modules as possible

The idea was that you’d pick the size you needed. In practice, it created a headache: packages had dependency conflicts, module sets were frozen at compile time, and maintaining three flavours in sync was a nightmare. So in NGINX 1.22.1-6 (Debian unstable), the Debian team pulled the plug. All three variants were removed from the official repository.

Why Is This Actually Good News?

Because the replacements are genuinely better. The old nginx-full was frozen with whatever modules Debian decided to compile in. You couldn’t add a module without recompiling from scratch. With modern NGINX, you get dynamic modules — loadable .so files you can add or remove by editing a config line. No recompile. No flavour selection at install time.

At deb.myguard.nl, we ship NGINX and Angie packages with 50+ dynamic modules, compiled with performance optimisations (-O3, -flto, jemalloc, zlib-ng), linked against our dedicated openssl-nginx build, and updated within hours of upstream releases.

Option 1: Install NGINX from the Official NGINX Repository

The NGINX project maintains its own APT repository at nginx.org. Latest stable or mainline release, built by the NGINX team themselves. No Debian packaging lag.

curl https://nginx.org/keys/nginx_signing.key | gpg --dearmor 
  | tee /usr/share/keyrings/nginx-archive-keyring.gpg >/dev/null

echo "deb [signed-by=/usr/share/keyrings/nginx-archive-keyring.gpg] 
  http://nginx.org/packages/debian $(lsb_release -cs) nginx" 
  | tee /etc/apt/sources.list.d/nginx.list

apt update && apt install nginx

New to the myguard repository? Follow the setup guide to add it in under a minute.

Solid choice for vanilla NGINX. Lacks HTTP/3 and most third-party modules though.

Option 2: NGINX or Angie from myguard (Recommended)

This is the option we’d recommend. Our packages include everything nginx-full had, plus HTTP/3, brotli, zstd, ModSecurity WAF, Lua, NJS, and 40+ other dynamic modules. You pick what you want at runtime by loading or not loading individual modules.

# Add the myguard repository
wget -qO- https://deb.myguard.nl/gpg.key 
  | gpg --dearmor > /usr/share/keyrings/myguard-archive-keyring.gpg
echo "deb [signed-by=/usr/share/keyrings/myguard-archive-keyring.gpg] 
  https://deb.myguard.nl stable main" 
  | tee /etc/apt/sources.list.d/myguard.list
apt update

# Install NGINX
apt install nginx

# Or install Angie (native ACME + JSON API, 100% NGINX-compatible)
apt install angie

Option 3: nginx-minimal (Principle of Least Privilege)

Running WordPress, a PHP app, or a reverse proxy? You don’t need 50 modules. nginx-minimal is the same performance-optimised NGINX with 12 rarely-used static modules stripped out. Smaller attack surface, same speed — great for Docker images and security-conscious deployments.

Option 4: Angie — The Modern NGINX Fork

Angie is maintained by the original NGINX core team. 100% config-compatible with NGINX, but adds native Let’s Encrypt support (no Certbot!), a JSON status API, and a faster release cycle. If you’re starting fresh, it’s worth considering.

Migration Checklist

  1. Back up your config: tar -czf /tmp/nginx-backup.tar.gz /etc/nginx/
  2. Add the myguard repository (see above)
  3. Install nginx or angie: apt install nginx or apt install angie
  4. Test config: nginx -t or angie -t
  5. Reload: systemctl reload nginx or systemctl reload angie
  6. Verify your site works — check HTTPS, check a few pages
  7. Install extra modules you need: apt install libnginx-mod-http-brotli etc.

Your existing /etc/nginx/ config files work without changes. The deprecation only affects the package name, not the software itself.

Modern NGINX replacement for deprecated nginx-full nginx-core nginx-light packages
The modern replacement for nginx-full: better performance, 50+ dynamic modules, HTTP/3

Frequently Asked Questions

Will removing nginx-full break my running site?
Not immediately — the package removal is a Debian repo change, not a forced uninstall. Your currently-installed nginx-full keeps running. But you won’t get security updates, so migrate soon.
Do I need to change my nginx.conf when migrating?
Almost certainly not. The core configuration syntax hasn’t changed. You may need to add a load_module line if you’re using a module that’s now dynamic rather than compiled-in, but that’s a two-second fix.
What is the difference between NGINX and Angie?
Angie is a fork of NGINX with added features: native ACME (Let’s Encrypt without Certbot), a JSON status API, and faster monthly releases. It’s 100% config-compatible with NGINX. See our full Angie vs NGINX comparison for details.
What about nginx-extras? Is that also deprecated?
Yes — nginx-extras was deprecated alongside nginx-core, nginx-full, and nginx-light. Same situation, same fix. Use the myguard packages which include all the extras as dynamic modules.
Is nginx-minimal the same as nginx-light?
Similar idea, better execution. nginx-light was a compile-time fixed module set. nginx-minimal from myguard strips 12 static modules you likely don’t need while keeping all 50+ dynamic modules available as opt-in installs.
Can I have both NGINX and Angie installed at the same time?
No — they both want ports 80 and 443. Pick one. The migration from NGINX to Angie takes about 5 minutes and your config works without changes.

Related Posts