cloudflare
nginx-proxy
cloudflare | nginx-proxy | |
---|---|---|
10 | 102 | |
371 | 18,045 | |
5.4% | 0.5% | |
5.1 | 8.8 | |
about 1 month ago | 6 days ago | |
Go | Python | |
Apache License 2.0 | MIT License |
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.
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
nginx-proxy
-
Can someone kindly suggest how to rate limit your node.js API when using nginx-proxy/nginx-proxy
I have an express API that runs on EC2 and I am using nginx-proxy
-
Working on Multiple Web Projects with Docker Compose and Traefik
If Traefik is not your thing Im happily using https://github.com/nginx-proxy/nginx-proxy and sslip.io for local docker compose development.
And then even plain nginx to proxy to non docker services...
(And ipv6 for really short urls. E.g. `example.com.--1.sslip.io` etc)
-
Build a Typescript Tool to modify npm automatically when using docker-containers
I wanted to share with you an exciting new tool that simplifies the process of interacting with the NGINX Proxy Manager API. It's a TypeScript tool that generates API requests based on environment variables within a Docker container. This tool is heavy influenced by the https://github.com/nginx-proxy/nginx-proxy but it works with npm.
-
Docker Services question
I use an automatically configuring reverse proxy - there's several to choose from, but the nginx-docker image is really nice, and comes with another image to do automatic SSL with certbot (if you wanted to host things externally).
-
Raspberry Pi 3b+ enough for proxy server
Docker runs on the 3B+ so you could use this [Github] or the one I have deployed here [NGINX Proxy Manager site] amongst others.
-
URL Rewriting exceptions for specific path - nginx with EJBCA PKI
- and this
-
Docker compose or kubernetes for single node cluster?
docker compose + wildcard dns + reverse proxy that covers all widecard subdomains + https://github.com/nginx-proxy/nginx-proxy (not to be confused with nginx itself) then setup a container for each app and set a subdomain for it, you can add ssl if you have a public domain or use self signed certs (but you need to distribute it to all machines and devices)
-
Beginner questions about deploying node.js app on Beanstalk
setting up letsencrypt with nginx-proxy and acme-companion
-
Using https with docker - managing TLS certificates from Lets Encrypt?
We use the nginx-proxy docker image. Auto-configuring reverse proxy with support for certbot. Never been easier - just put your domain and certbot details in your container env, and it does the rest.
-
Am I headed in the right direction to setup SSL for certbot inside docker with nginx?
I just use the nginx-proxy image, makes it all super easy, auto-configuring, and all domain/cert information is stored against the project rather than the proxy.
What are some alternatives?
Nginx Proxy Manager - Docker container for managing Nginx proxy hosts with a simple, powerful interface
unbound
acme-companion - Automated ACME SSL certificate generation for nginx-proxy
crowdsec - CrowdSec - the open-source and participative security solution offering crowdsourced protection against malicious IPs and access to the most advanced real-world CTI.
Laradock - Full PHP development environment for Docker.
caddy-docker - Source for the official Caddy v2 Docker Image
vouch-proxy - an SSO and OAuth / OIDC login solution for Nginx using the auth_request module
caddy-docker-proxy - Caddy as a reverse proxy for Docker
authentik - The authentication glue you need.
docker-pi-hole - Pi-hole in a docker container
docker-swag - Nginx webserver and reverse proxy with php support and a built-in Certbot (Let's Encrypt) client. It also contains fail2ban for intrusion prevention.