Back from the weekend. In general I suspect weekends will be consistent blank spots in my #DecemberAdventure-ing, as activities and parenting and napping make it challenging to do much else. But who knows!
Anyway, today I eased back into things by doing some research into using Traefik as a reverse proxy for external services. Indeed, it seems entirely possible, even if that Reddit thread makes absolutely no mention of the solution.
At this point, I need to figure out a good testing setup. I need a way to get rapid feedback that things are working at each step of the process, rather than flicking the switch at the very end and wondering which of the two dozen steps before it is the one with the problem. Here’s what I’m thinking:
- Pick a single external service to start with (e.g., JellyFin—it’s already running)
- Design a Service and IngressRoute for JellyFin
- Add the JellyFin entry to my Firewalla DNS
- Do NOT use SSL, at least initially
I figure SSL is going to be its own thing, since I need a wildcard DNS cert from Cloudflare and a whole configuration via cert-manager. So this might be more of a “part 2” once I get the above bullets working. Just proving that Traefik can manage reverse proxy requests for external services will be enough proof of concept to move forward with other parts, like SSL.
I guess I’m just apprehensive, since this will require modifying my current Traefik configuration that successfully serves up my Mastodon instance. Obviously I can always revert configurations if everything breaks, but… well, I hate messing with what already works. But I know it’ll be infinitely more flexible and maintainable going forward if I’m successful.
Citation
@online{quinn2024,
author = {Quinn, Shannon},
title = {December {Adventure:} {I} Have a Bad Feeling about This},
date = {2024-12-09},
url = {https://magsol.github.io/2024-12-09-december-adventure-i-have-a-bad-feeling},
langid = {en}
}