Traefik-v2-examples
cloudflare
Traefik-v2-examples | cloudflare | |
---|---|---|
10 | 10 | |
588 | 364 | |
- | 3.6% | |
0.0 | 5.1 | |
3 months ago | 30 days ago | |
Go | ||
- | Apache License 2.0 |
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.
Traefik-v2-examples
-
nginx proxy manager.....driving me insane
Theres also traefik guide but the contrast in complexity is apparent right away.
-
I'm new to self hosting. How do you choose which reverse proxy to use?
Traefik that I tried first is very powerful but there are few abstraction layers and bit of complexity that I felt like I had to re-learn it every time I was about to do a change. But it is very powerful in dynamic enviroments where one spins often enough more new containers.
-
Which reverse proxy are you using?
My first reverse proxy was traefik, but it was just too complex, with too many abstraction layers for my use. I needed to re-learn it every time I went to make changes.
-
How do I use a domain name for local services?
I tried traefik. As I was learning it, which was like a week or two of effort, I actually wrote a guide that somehow got 500 stars on github...
-
Proxy Reverse alternative?
Theres also traefik, that people recommend, but IMO for home stuff it is too complex with too many abstractions. Caddy is literally just giving it port 80 and 443 and a single clean config file.
-
Let'sEncrypt certificate on a daily changing docker container.
Traefik is actuall business aimed and powerful and probably worth learning if you would need to manage lot of containers and change stuff dynamically on the fly. But it is just so damn complicated and you kinda need to re-learn it every time you return to it. Here is guide for that one..
-
Traefik with Let's Encrypt using DuckDns domain
You can try look here
-
Best way to learn Traefik?
Here is a decent guide that gets you going.
-
My docker network is already complete, but I'm considering adding traefik. Is there a simple way to retroactively apply it to around 30 existing dockers?
Have you considered going caddy instead of traefik?
-
Which reverse proxy do you use?
How to reverse proxy with traefik
cloudflare
-
Which reverse proxy are you using?
If you're using Cloudflare then you might need the Cloudflare module which is a little annoying because you need to rebuild the Caddy executable (or Docker image) to include it. I just set up a GitHub repo that uses GitHub Actions to build and publish a Docker image that includes the Caddy Docker Proxy and Cloudflare modules, but I haven't figured out how automatically update the image when a new version of Caddy is released so it's still a manual process for now.
-
Help: Caddy setup for internal LAN access only
if domain.xyz is already pointed to cloudflare's nameservers, you'll want to use the cloudflare dns plugin with caddy for a wildcard tls cert from letsencrypt.
-
Story on revisiting Svelte/Kit after moving to Solid, then Remix
I'm on Cloudflare now, so I build my own image based on this Docker image to use SSL from Cloudflare.
-
Caddy2 reverse proxy to pihole not working
Anyways, my end goal is to use cloudflare aswell, because I see that then you can get a wildcard DNS record. Have you tried that? Are you using https://github.com/caddy-dns/cloudflare ? Did you have to build it yourself, or is it included in dockerhub image?
- Komga & caddyserver2 are driving me insane.
-
NGINX Proxy Manager
> First, what versions am I getting? Does using `2.5.1-builder` result in a customer built binary that's version `2.5.1`? The command usage [1] of the `xcaddy` command says it falls back to the `CADDY_VERSION` environment variable if it's not set explicitly. Since it's not set explicitly, I go looking for that variable in the Dockerfile [2].
Yeah - the default version it'll build with is the version embedded in the builder image, so in that case, v2.5.1. But really, you can just use always use the latest builder image and specify the version you want in the xcaddy command, i.e. 'xcaddy build v2.5.1 --with ', or any other git ref if not a version (cause we're using Go to build and you can use any git ref, like a commit hash or branch name if you want to try a WIP pull request).
We set it up with a good default so most users wouldn't need to ask that question, it should "just work" for them. But it's a valid question to ask.
> That's some templating language I'm not familiar with and I can't track down where the variable gets set, at least not quickly.
Yeah we're using Gomplate for generating the Dockerfiles for the official Docker Library builds, since we need to make builds for every CPU architecture, and even Windows docker images (I still have no idea why anyone would want those, but alas). Either way, that's an implementation detail of how we automate this stuff, doesn't matter to users.
> Now, what version of `caddy-dns/cloudflare` am I getting?
The latest, if you don't specify a version. The https://github.com/caddy-dns/cloudflare repo doesn't have tagged releases, so it'll just be the latest commit on the master branch. You can specify a specific commit like '--with github.com/caddy-dns/cloudflare@8ea1cff' for (as of this writing) the commit just before the latest.
> What other risks come along with building and maintaining my own custom image?
Honestly, none. Maybe problems with plugins not being compatible with eachother, but Caddy's plugin design means that should rarely happen, except if two plugins have the same module ID. But that's up to you to make sure you don't pick two plugins that try to do the same thing.
Because of the way Go builds work, they can always be cross-compiled. We don't use CGO, so builds of Caddy are completely static and have zero dependencies. There's really no risk that it doesn't build in a specific environment, or whatever.
> If I build a custom image, do I let other people I help with the odd tech thing use it or is all the effort for me only? I don't want to become the maintainer of a Docker image others rely on, so I can't even re-use any related config if I help others in the future since they won't have access to the needed image.
Up to you. But that's the exact reason we don't maintain builds with plugins ourselves. There's literally an infinite amount of combinations possible. Some have suggested like "caddy-lite" and "caddy-full" sort of setups where we ship just a few vetted plugins or "yolo give me all the plugins" but that's silly. We don't have the time or resources to vet all the plugins.
From your perspective it might seem like "duh, there should be an official build with Cloudflare", but really it's a pretty small percentage of users who need this.
> Also, a 4 line Docker file looks nice in terms of being simple, but explicitly declaring or even adding comments describing some of the things I pointed out above can save people a lot of time. Even comments with links to the relevant portions of the docs would be super useful.
(as I wrote in my other comment, the docs for this are on https://hub.docker.com/_/caddy)
> The desire for wildcard certificates is to keep things from being discoverable via CTLogs.
It's really trivial for someone to scan until they hit subdomains that return a successful response, if they really cared. This doesn't really protect from anything. Using wildcards for that is a bit of an antipattern.
- Best Applications To Use For 2FA For VPN Connections Into Local LAN?
-
Can't access website from outside local network.
For more, see: https://github.com/caddy-dns/cloudflare
-
3 weeks ago I knew nothing about docker or selfhosting. Now I have my small home server and thanks to r/selfhosted I was able to setup it all by myself! Any recommendations on what should I install next?
As default it does need port 80 open to renew certificates, but you can use DNS challenge instead. https://github.com/caddy-dns/cloudflare
What are some alternatives?
mistborn
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
selfhosted-apps-docker - Guide by Example
unbound
self-hosted-cookbook - A cookbook, for docker-compose based recipes, for self-hosted applications and services.
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
caddy-docker - Source for the official Caddy v2 Docker Image
Caddy - Fast and extensible multi-platform HTTP/1-2-3 web server with automatic HTTPS
caddy-docker-proxy - Caddy as a reverse proxy for Docker
Cosmos-Server - ☁️ The Most Secure and Easy Selfhosted Home Server. Take control of your data and privacy without sacrificing security and stability (Authentication, anti-DDOS, anti-bot)
docker-pi-hole - Pi-hole in a docker container