← Directory

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 2 of 6 install platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)

Also on Docker Hub and GitHub

Health score

15/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

How is this calculated?

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). Factors without data are left out and the rest are rescaled.

Availability: platform listings confirmed today

No GitHub repository data collected yet.

Checked 7 days ago - source: GitHub (BigBearTechWorld/swag)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 7 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 6 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 2 days ago - public community threads