SWAG

SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php…

  • Home Automation
  • Network Services
  • Security
  • Tools & Utilities
SWAG - Secure Web Application Gateway (formerly known as letsencrypt, no relation to Let's Encrypt™) sets up an Nginx webserver and reverse proxy with php support and a built-in certbot client that automates free SSL server certificate generation and renewal processes (Let's Encrypt and ZeroSSL). It also contains fail2ban for intrusion prevention.

Platform availability

Available on 3 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

75/100 Good

Maintained
100last commit 21 days ago
Popular
713,754 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
404 GB minimum RAM, runs on ARM

Availability: platform listings confirmed today, links checked 11 days ago

GitHub stars
3,754
Open issues
11
Last commit
2026-10-31
Latest release
5.9.0-ls497
License
GPL-3.0
Activity
steady

Checked 17 days ago - source: GitHub (linuxserver/docker-swag)

Resources & Compatibility

Minimum requirements: 4 GB RAM, 700 MB disk. ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Set PUID/PGID to your host IDs Run `id your_user` on your server, then put those numbers into PUID and PGID (the user and group IDs the container runs as). This stops permission errors when you later try to open, delete, or back up the app's files. source
  • Map the web ports before starting Add the ports you need in the compose/run settings using the host-port:container-port pattern shown as `-p 8080:80`. Without the right mapping, you cannot reach the app from your browser or other devices. source
  • Keep /config in a safe folder Point a folder on your server to the container's /config path, like the example shows. That folder holds the app's settings, so keeping it safe and backed up prevents a total reset if the container is recreated. source

Fetched 53 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What do you change in a SWAG proxy conf when using a subdomain other than the preset one?

Change the server name in the proxy conf to match the subdomain you want to use.

What port or DNS-related issue can appear when running SWAG on a local network?

You may run into conflicts involving ports 443 and 444, especially with split DNS or dnsmasq, and you need to account for multiple subdomains.

Why is SWAG often suggested to people new to reverse proxies?

It includes certbot and the needed config files, which is useful for first-time reverse proxy setups.

How are LinuxServer images updated?

They are automatically rebuilt when upstream applications or application dependencies are updated.

Answers sourced from discourse.linuxserver.io, linuxserver.io, www.reddit.com, www.reddit.com

Community

Collected 48 days ago - public community threads