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.
Thread
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.