Good afternoon dear Fluxer Team,
Caddy, or Traefik, are in my opinion a blight on the infrastructure. Many systems are already in place (almost always without Caddy/Traefik), and I would like to use a server I already own and have setup infrastructure on (pure NGINX in this case), rather than having to buy a completely new server just for Fluxer, as Fluxer's current setup would overwrite my entire network stack.
Your current documentation and template is basically intertwined with Caddy and nearly impossible to remove without major issues. The problem is that most people do not necessarily use Caddy (or Traefik for that matter), and so if you'd be so kind as to write reverse-proxy neutral Docker templates, that would be really helpful. Because when you do, everyone can use whichever one they like, be it Caddy, Traefik, NPM, pure NGINX, etc.
Best regards,
Would like it if there was a template that works with LAN only setup that does not use a reverse proxy. Would likely be an easier and faster way to spin it up to give it a try and/or if you just want to keep it LAN only (or access it remotly with VPN like Wireguard).
Status changed from Under consideration to ShippedStatusUnder consideration→Shipped
The stack now runs behind any reverse proxy without Caddy. See https://docs.fluxer.app/operator/reverse-proxy/ for the docker-compose.proxy.yml overlay and examples for nginx, Traefik, HAProxy and others.
i was looking for anyone who wanted a more agnostic approach to self hosting too! i've found a couple of comments mentioning people putting it behind nginx, even in another issue, but no actual steps or a rough template of the expected headers and parameters fluxer actually wants; im super stoked for the official launch of the docs -albeit still in progress-, but being able to switch caddy for any other reverse proxy would be awesome
i was looking for anyone who wanted a more agnostic approach to self hosting too! i've found a couple of comments mentioning people putting it behind nginx, even in another issue, but no actual steps or a rough template of the expected headers and parameters fluxer actually wants; im super stoked for the official launch of the docs -albeit still in progress-, but being able to switch caddy for any other reverse proxy would be awesome
I would suggest that you share this issue with others who want to self-host, so that we get more visibility on this and have it fixed as soon as possible. That way, Fluxer self-hosting will take off a lot faster as well.
Agreed making caddy basically the only option is a bad idea imo, sure it leads to less "headaches" when it comes to issues with self-hosting having it all focused on one single stack as you don't have to constantly try it out between different web servers and how they might just handle stuff slightly different, but I myself also mainly use NGINX as a reverse-proxy via npmplus for all my applications and obviously there are many more that use just NGINX by itself or Traefik
RexSystem1 voteoriginally by @LokeYourC3PH on GitHub OP
Agreed making caddy basically the only option is a bad idea imo, sure it leads to less "headaches" when it comes to issues with self-hosting having it all focused on one single stack as you don't have to constantly try it out between different web servers and how they might just handle stuff slightly different, but I myself also mainly use NGINX as a reverse-proxy via npmplus for all my applications and obviously there are many more that use just NGINX by itself or Traefik
The problem in particular is how absolutely crazily intertwined Caddy is into this stack. It isn't just added next to Fluxer, or on top of it, so you can just remove it and replace the one env. variable that calls for it. Nope, aside from Caddy itself being a part of the stack which is removable, there are multiple calls directly to Caddy from other parts of the stack. Looking at the Caddy file, you can adapt it to NGINX proxy templates, that isn't a huge deal in and of itself. The major issue is that the stack basically expects Caddy to be present, and I have no idea what will happen if you just rip it out.
the original post seems to be a little aggressive against Caddy... but it look me about 15 seconds to remove the dependency
Nginx doesn't support zstd and http3 without a lot of messing around. Caddy doesn't support caching without compiling a module and traefik is overkill in most cases...
There isn't a simple middle ground for me.....and a lot of us are throwing cloudflare tunnels or even pangolin in front of this so it's kind of a reverse proxy sandwich.
The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.
the original post seems to be a little aggressive against Caddy... but it look me about 15 seconds to remove the dependency
Nginx doesn't support zstd and http3 without a lot of messing around. Caddy doesn't support caching without compiling a module and traefik is overkill in most cases...
There isn't a simple middle ground for me.....and a lot of us are throwing cloudflare tunnels or even pangolin in front of this so it's kind of a reverse proxy sandwich.
The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.
hey @shleeable could you share how you did it? i'd love to see it.
i personally have no issues with caddy being a critical portion of the stack as i understand the limitations you bring up of these solutions, but i think it would be great if the documentation could point to a way that caddy resolves the things it needs like zstd and http3 and just give nginx or any other reverse proxy what it needs to properly communicate with fluxer
RexSystem1 voteoriginally by @InsertDisc on GitHub
What needs fixing?
Good afternoon dear Fluxer Team,
Caddy, or Traefik, are in my opinion a blight on the infrastructure. Many systems are already in place (almost always without Caddy/Traefik), and I would like to use a server I already own and have setup infrastructure on (pure NGINX in this case), rather than having to buy a completely new server just for Fluxer, as Fluxer's current setup would overwrite my entire network stack.
Your current documentation and template is basically intertwined with Caddy and nearly impossible to remove without major issues. The problem is that most people do not necessarily use Caddy (or Traefik for that matter), and so if you'd be so kind as to write reverse-proxy neutral Docker templates, that would be really helpful. Because when you do, everyone can use whichever one they like, be it Caddy, Traefik, NPM, pure NGINX, etc.
Best regards,
Maybe you have very specific circumstances but changing the host port for Caddy in the compose file to something else, say 8180, and commenting out the others, and then following the cloudflared tunnel setup (without actually using Cloudflare) the rest of the way allowed me to just point my reverse proxy at 8180 http without issue.
RexSystem1 voteoriginally by @IamLurking on GitHub
Maybe you have very specific circumstances but changing the host port for Caddy in the compose file to something else, say 8180, and commenting out the others, and then following the cloudflared tunnel setup (without actually using Cloudflare) the rest of the way allowed me to just point my reverse proxy at 8180 http without issue.
I'm really confused how you made it work without Caddy. Following what you said you did and still cannot access chat.[redacted].com.
I changed the Caddy port to 8181, commented the 443 ports, changed FLUXER_CADDY_SITE_ADDRESS=:8181
I am a new user of Caddy, that is not on the same host as fluxer, I cannot have 2 caddy setup and just cannot seem to figure out how to make it work....
I have also tried with cloudflare tunnel and it doesn't work either... I just get a blank page...
RexSystem1 voteoriginally by @InsertDisc on GitHub
> Maybe you have very specific circumstances but changing the host port for Caddy in the compose file to something else, say 8180, and commenting out the others, and then following the cloudflared tunnel setup (without actually using Cloudflare) the rest of the way allowed me to just point my reverse proxy at 8180 http without issue.
I'm really confused how you made it work without Caddy. Following what you said you did and still cannot access chat.[redacted].com. I changed the Caddy port to 8181, commented the 443 ports, changed FLUXER_CADDY_SITE_ADDRESS=:8181
I am a new user of Caddy, that is not on the same host as fluxer, I cannot have 2 caddy setup and just cannot seem to figure out how to make it work.... I have also tried with cloudflare tunnel and it doesn't work either... I just get a blank page...
the original post seems to be a little aggressive against Caddy... but it look me about 15 seconds to remove the dependency
Nginx doesn't support zstd and http3 without a lot of messing around. Caddy doesn't support caching without compiling a module and traefik is overkill in most cases...
There isn't a simple middle ground for me.....and a lot of us are throwing cloudflare tunnels or even pangolin in front of this so it's kind of a reverse proxy sandwich.
The caddyfile is simply enough with just basic path based redirections so I'm planning on trying pangolin without caddy.
@shleeable I dont suppose you got anywhere with using pangolin at all?
RexSystem1 voteoriginally by @LokeYourC3PH on GitHub OP
> > Maybe you have very specific circumstances but changing the host port for Caddy in the compose file to something else, say 8180, and commenting out the others, and then following the cloudflared tunnel setup (without actually using Cloudflare) the rest of the way allowed me to just point my reverse proxy at 8180 http without issue.
>
>
> I'm really confused how you made it work without Caddy. Following what you said you did and still cannot access chat.[redacted].com. I changed the Caddy port to 8181, commented the 443 ports, changed FLUXER_CADDY_SITE_ADDRESS=:8181
> I am a new user of Caddy, that is not on the same host as fluxer, I cannot have 2 caddy setup and just cannot seem to figure out how to make it work.... I have also tried with cloudflare tunnel and it doesn't work either... I just get a blank page...
FLUXER_CADDY_SITE_ADDRESS=:80
Caddy port in compose 8181:80
Everything else is fine. Point reverse proxy at 8181.
Check my comment here https://github.com/orgs/fluxerapp/discussions/1041
This was the way for me, works with bare NGINX and my proxy template from HestiaCP adjusted to use the (on my end) 8585 port. Only issue I had is that I didn't comment out 443 for SSL, and so it couldn't launch. All I did was assign 443 another port like for 80 to 8585, to 8586, and that solved the issue. I don't use the SSL port and merely did the redirect to Caddy part, and it works perfectly fine for me now.
RexSystem1 voteoriginally by @Gelantious on GitHub
Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
So pretty please, give us options.
RexSystem1 voteoriginally by @InsertDisc on GitHub
Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
So pretty please, give us options.
I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
You only have to set
FLUXER_CADDY_SITE_ADDRESS=:80
And pick whatever you want for the Caddy port.
1234:80
done.
RexSystem1 voteoriginally by @InsertDisc on GitHub
How do you port forward 7881/tcp and 7882/udp for LiveKit media? Is it also handled by Nginx?
You could probably do streams, but it's just a regular straight port forward as they don't carry host header information. Just forward those ports to the machine running fluxer. Unless it's a public facing VPS, then you would just need to open them in your firewall.
I should have specified, I meant for IPv6.
In my registrar I can add a record for fluxer.mydomain.tld so it points to my public IPv4, which is the same for fluxer or Nginx and the firewall will forward depending on the port. However for IPv6 I need to add 2 records for 2 different IPs since they're globally routable, aside from streams is there a way to deal with this that I don't know about?
RexSystem1 voteoriginally by @InsertDisc on GitHub
I should have specified, I meant for IPv6.
In my registrar I can add a record for fluxer.mydomain.tld so it points to my public IPv4, which is the same for fluxer or Nginx and the firewall will forward depending on the port. However for IPv6 I need to add 2 records for 2 different IPs since they're globally routable, aside from streams is there a way to deal with this that I don't know about?
I don't know a whole lot about ipv6 but I'm pretty sure you want your A and AAAA records to point to whatever is doing your ssl termination. You'd have to just redirect the ports from your nginx machine to the fluxer machine directly or incorporate an l4 proxy in front of nginx.
This is getting a bit off topic though.
RexSystem1 voteoriginally by @RikudouGoku on GitHub
> Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
> So pretty please, give us options.
I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
You only have to set FLUXER_CADDY_SITE_ADDRESS=:80 And pick whatever you want for the Caddy port. 1234:80 done.
> > Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
> > So pretty please, give us options.
>
>
> I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
> You only have to set FLUXER_CADDY_SITE_ADDRESS=:80 And pick whatever you want for the Caddy port. 1234:80 done.
I assume this is a different issue?
image
Yes. I've been using the aforementioned method to put Traefik in front of Caddy without issues.
RexSystem1 voteoriginally by @RikudouGoku on GitHub
> > > Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
> > > So pretty please, give us options.
> >
> >
> > I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
> > You only have to set FLUXER_CADDY_SITE_ADDRESS=:80 And pick whatever you want for the Caddy port. 1234:80 done.
>
>
> I assume this is a different issue?
> image
Yes. I've been using the aforementioned method to put Traefik in front of Caddy without issues.
Weird as i get the same error when i use the http link....
> > > > Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
> > > > So pretty please, give us options.
> > >
> > >
> > > I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
> > > You only have to set FLUXER_CADDY_SITE_ADDRESS=:80 And pick whatever you want for the Caddy port. 1234:80 done.
> >
> >
> > I assume this is a different issue?
> > image
>
>
> Yes. I've been using the aforementioned method to put Traefik in front of Caddy without issues.
Weird as i get the same error when i use the http link....
Is there anything useful in the browser console on container logs?
RexSystem1 voteoriginally by @RikudouGoku on GitHub
> > > > > Would very much like an option without caddy as most of us in the self-hosting world already have a reverse proxy system in place for other things we host. Having to go through editing this and possibly having it break in the future, resulting in more time spent troubleshooting isn't that alluring :)
> > > > > So pretty please, give us options.
> > > >
> > > >
> > > > I've been using NPM for years and do with Fluxer as well. It's two config lines to use your own reverse proxy. Put the stack on 80 internally so it doesn't do certs and set a host port. That's simpler than some other services... how can this be easier?
> > > > You only have to set FLUXER_CADDY_SITE_ADDRESS=:80 And pick whatever you want for the Caddy port. 1234:80 done.
> > >
> > >
> > > I assume this is a different issue?
> > > image
> >
> >
> > Yes. I've been using the aforementioned method to put Traefik in front of Caddy without issues.
>
>
> Weird as i get the same error when i use the http link....
Is there anything useful in the browser console on container logs?
@RikudouGoku the screenshot shows that it's a CORS issue; your browser is making requests to 192.168.0.153 instead of an actual domain, which I assume should be fluxer.<something>.dedyn.io in your case.
How exactly did you set this up? If you're unsure, I'd suggest starting over and following the docs exactly. Assuming you have Traefik set up and working, the only thing you should have to change is FLUXER_CADDY_SITE_ADDRESS=:80 in your .env file.
PSA: If you or anyone else wants quicker help then the #self-hosting channel in the Fluxer Developers community is pretty active.
@RikudouGoku the screenshot shows that it's a CORS issue; your browser is making requests to 192.168.0.153 instead of an actual domain, which I assume should be fluxer.<something>.dedyn.io in your case.
Note that i get this same issue even if i use the http://192.160.0.153:1234/ link instead. And not the https link (dedyn.io).
I spun up a nginx proxy manager plus and added my fluxer.redacted.dedyn.io and created a cert for it then made a proxy host for it pointing to the lan ip being 192.168.0.153 and the forward port being 1234, TLS settings being to have "force https", "HSTS Enabled", "HTTP/3 Support" and "HSTS Subdomains+Preload" turned on.
(im doing all this on my test server.)
How exactly did you set this up? If you're unsure, I'd suggest starting over and following the docs exactly. Assuming you have Traefik set up and working, the only thing you should have to change is FLUXER_CADDY_SITE_ADDRESS=:80 in your .env file.
And yes i did change that fluxer caddy site address to that exactly.
I did comment out the 443:443 ports for caddy though since i needed that port for npm.
So this part:
RexSystem1 voteoriginally by @lazy-media on GitHub
Not sure if this was mentioned, I kind of scanned through the comments and didn't see this mentioned, but with Caddy, if you want to have caddy just pass through the traffic and assume there is another reverse proxy available to handle certificates, you can enter in your FLUXER_CADDY_SITE_ADDRESS as something like http://fluxer.example.com instead of example.com and it will serve Fluxer on port 80 instead of 443 and if you have it setup through another reverse proxy.
Example: FLUXER_CADDY_SITE_ADDRESS=http://fluxer.example.com
I personally use Authentik as my reverse proxy and I did this with my Fluxer instance and pointed Authentik to the Fluxer internal IP address and port 80. Works fine for me, but it prefers to use the domain name instead of local address for accessing.
I found this solution here: https://caddy.community/t/running-a-caddy-server-behind-another-solved/13122/7
Hope this is helpful. Also wish this would have been mentioned in their documentation.
Systemoriginally by @RikudouGoku on GitHub
28 comments
Comment by Rex
Comment by @concienciadesventurada
Comment by @LokeYourC3PH
Comment by @Mar0xy
Comment by @LokeYourC3PH
Comment by @shleeable
Comment by @RikudouGoku
Comment by @retropele
Comment by @concienciadesventurada
Comment by @InsertDisc
Comment by @IamLurking
Comment by @InsertDisc
Comment by @kazak-99
Comment by @LokeYourC3PH
Comment by @Gelantious
Comment by @InsertDisc
Comment by @Jerroder
Comment by @InsertDisc
Comment by @Jerroder
Comment by @InsertDisc
Comment by @RikudouGoku
620100432-f9fcaaaf-d0b0-41ed-8539-28f3a113cee1.png
653×741 | 109 kB
Comment by @mvahaste
620100432-f9fcaaaf-d0b0-41ed-8539-28f3a113cee1.png
653×741 | 109 kB
Comment by @RikudouGoku
620100432-f9fcaaaf-d0b0-41ed-8539-28f3a113cee1.png
653×741 | 109 kB
Comment by @mvahaste
620100432-f9fcaaaf-d0b0-41ed-8539-28f3a113cee1.png
653×741 | 109 kB
Comment by @RikudouGoku
620100432-f9fcaaaf-d0b0-41ed-8539-28f3a113cee1.png
653×741 | 109 kB
620417946-9a61424d-b6ae-497a-8e99-8cfa6631a3bd.png
1657×810 | 445 kB
Comment by @mvahaste
192.168.0.153instead of an actual domain, which I assume should befluxer.<something>.dedyn.ioin your case. How exactly did you set this up? If you're unsure, I'd suggest starting over and following the docs exactly. Assuming you have Traefik set up and working, the only thing you should have to change isFLUXER_CADDY_SITE_ADDRESS=:80in your.envfile. PSA: If you or anyone else wants quicker help then the#self-hostingchannel in the Fluxer Developers community is pretty active.Comment by @RikudouGoku
Comment by @lazy-media
FLUXER_CADDY_SITE_ADDRESSas something likehttp://fluxer.example.cominstead ofexample.comand it will serve Fluxer on port 80 instead of 443 and if you have it setup through another reverse proxy. Example:FLUXER_CADDY_SITE_ADDRESS=http://fluxer.example.comI personally use Authentik as my reverse proxy and I did this with my Fluxer instance and pointed Authentik to the Fluxer internal IP address and port 80. Works fine for me, but it prefers to use the domain name instead of local address for accessing. I found this solution here: https://caddy.community/t/running-a-caddy-server-behind-another-solved/13122/7 Hope this is helpful. Also wish this would have been mentioned in their documentation.Deleted comment