awesome-selfhosted
docker-swag
| awesome-selfhosted | docker-swag | |
|---|---|---|
| 1 | 296 | |
| 7 | 2,561 | |
| - | 2.2% | |
| 4.6 | 9.1 | |
| about 2 months ago | 3 days ago | |
| Dockerfile | ||
| - | GNU General Public License v3.0 only |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
awesome-selfhosted
-
Your top 5 best self hosted apps?
My complete list: timokoessler/awesome-selfhosted
docker-swag
- Take a look at traefik, even if you don't use containers
- Armar mi propio server
-
Guide: Setting up Local DNS WITH PORTS
I have a NAS on .0.181 and a swag container (on a different port than nginx) on .0.180 that points to my public facing services. For obvious reasons, I don't want my public domain to point to any other ports/addresses on my home network. Additionally, as elegant as swag is, it requires authentication and so won't work for simple local DNS. I now have one local domain for each server and an nginx instance on each that resolves to my different services on each.
-
SWAG + Nextcloud AIO + OnlyOffice + Openproject: Fullchain cert connections required. I have the data but I'm not sure how to plug this all together...
OP is even linking the Github... https://github.com/linuxserver/docker-swag
-
Reverse Proxied services not accessible on LAN
I have an UnRAID server with a few services (Jellyfin, Nextcloud, etc.) running on it behind Linux Servers' SWAG reverse proxy container, which is built on Nginx and Let's Encrypt. This is pointed to a DuckDNS link, which is then pointed at my domain with a CNAME. So I can access Jellyfin, for example, at jellyfin.mydomain.com. A few weeks ago, due to seemingly unrelated issues, I got a new modem/router, an Arris SURFboard G34. For the first few weeks, everything was working as before. But now, when on my LAN, I can't get to my services at the proxied domain. It times out every time. There are no errors in SWAG's logs, nothing seems amiss in the router's web interface, and the services are available both at their IP:port address and, when not on my LAN, I can access them at the domain no problem.
- Fail2Ban – Daemon to ban hosts that cause multiple authentication errors
- Mealie and Swag sut issues
- Can't get Swag instance page
- Site marked dangerous
- Reverse proxy, where to start?
What are some alternatives?
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
authentik - The authentication glue you need.
traefik-examples - docker-compose configurations examples for traefik
oauth2-proxy - A reverse proxy that provides authentication with Google, Azure, OpenID Connect and many more identity providers.
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
authelia - The Single Sign-On Multi-Factor portal for web apps
Navidrome Music Server - 🎧☁️ Modern Music Server and Streamer compatible with Subsonic/Airsonic
Jellyfin - The Free Software Media System
docker-pihole-unbound - Run Pi-Hole + Unbound on Docker
caddy-docker-proxy - Caddy as a reverse proxy for Docker
plex-nginx-reverseproxy - Configuration to serve Plex Media Center https://plex.tv using Nginx https://nginx.com
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.