If you’re dealing with this much storage, it’s time to upgrade to a rack. Don’t deal with having to shove 10 drives into a packed full-size.
Start scouring 2nd hand auction sites and buy one used. They’re pretty cheap as far as solutions go if you can grab them used. Something like this would be ideal: https://www.silverstonetek.com/en/product/info/server-nas/RM22-312/
It’s pretty great. The only thing you have to remember is that the caddy instance and the container you’re proxifying have to be within the same docker network. So you’ll definitely want to use the caddy2 container if this is the setup you want to pursue.
If not then you can just use IP addresses inside or outside of a container it doesn’t matter.
Then I found out my services would work better with Caddy
Exceptional idea. Cloudflare is nice, but Caddy will always win IMO. Additionally, considering you were able to get Caddy working, that simply drives home that unfortunately your reverse_proxy didn’t work because it was somehow misconfigured. Caddy is also a reverse_proxy.
My comment is pretty much what I said. You have an extremely complex environment that you’re not fully making use of. For example, you’re having issues with a reverse_proxy, but you had Tailscale presumably the whole time. Why not just use your VPN to reverse_proxy your requests if you were having issues?
Also using Caddy + Cloudflare is fine if you want to use cloudflare for DNS, however, Caddy handles all certificates itself. So you have Caddy, which can handle all the SSL certs itself, but you put Cloudflare on top of it to manage SSL certs. It’s just convoluted.
It’s a good environment, but a little overkill.
I really love home labs but this sounds incredibly over engineered for its purpose… I would expect a set up like this for an enterprise environment…
I very highly recommend that you take the time and just switch. Caddy is simply fabulous. It’s designed to work (assuming it’s compiled with the module) with containers and use docker networks for routing. It makes it easy to spin up containers and directly reference the container names instead of remembering IP addresses and particularly comes in handy when your entire environment is containerized.
You can pull the caddy image and run it in docker and as long as your environment is configured correctly you can simply reverse_proxy @container and you’re done. Caddy pulls all the relevant port information directly from the container API.
I get such a nerd boner thinking about it.
Every single action that he does even if it only takes a day to undo took decades to get implemented. Will probably take just as long to get it back.
Probably just easier to nix the Prime subscription and just download scene releases… Most of them are h265 these days and are released same day as on Prime.
I just checked a list of “new to prime” and my tracker and they were all there. No reason to give money to Amazon.