this post was submitted on 29 Jan 2025
22 points (86.7% liked)

Selfhosted

41554 readers
509 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 2 years ago
MODERATORS
ruud@lemmy.world
Loki@lemmy.world
CannaVet@lemmy.world
devve@lemmy.world
HybridSarcasm@lemmy.world
HybridSarcasm@lemmy.hybridsarcasm.xyz
22
Reverse proxy without a single point of failure (lemmy.sdf.org)
submitted 1 day ago by victory@lemmy.sdf.org to c/selfhosted@lemmy.world
22 comments fedilink hide all child comments
 

I'm thinking of expanding my homelab to support running some paid SaaS projects out of my house, and so I need to start thinking about uptime guarantees.

I want to set up a cluster where every service lives on at least two machines, so that no single machine dying can take a service down. The problem is the reverse proxy: the router still has to point port 443 at a single fixed IP address running Caddy, and that machine will always be a single point of failure. How would I go about running two or more reverse proxy servers with failover?

I'm guessing the answer has something to do with the router, and possibly getting a more advanced router or running an actual OS on the router that can handle failover. But at that point the router is a single point of failure! And yes, that's unavoidable... but I'm reasonably confident that the unmodified commodity router I've used for years is unlikely to spontaneously die, whereas I've had very bad luck with cheap fanless and single-board computers, so anything I buy to use as an advanced router is just a new SPOF and I might as well have used it for the reverse proxy.

you are viewing a single comment's thread
view the rest of the comments
[–] Shimitar@downonthestreet.eu 4 points 1 day ago* (last edited 1 day ago)

No, the router being the SPOF (single point of failure) is totally avoidable.

At mny home (no SaaS services offered, but critical "enough" for my life services) i have two different ISPs on two different tecnologies: one is FTTC via copper cable (aka good old ADSL successor) plus a WFA 5G (much faster but with data cap). Those two are connected to one opnSense router (which, indeed, is a SPOF at this time). But you can remove also this SPOF by adding a second opnSense and tie the two in failover.

So the setup would be:

  • FTTC -> ISP1 router -> LAN cable 1 to port 1 of opnSense n.1
  • FTTC -> ISP1 router -> LAN cable 2 to port 1 of opnSense n.2
  • FWA -> ISP2 router -> LAN cable 1 to port 2 of opnSense n.1
  • FWA -> ISP2 router -> LAN cable 2 to port 2 of opnSense n.2

Then in both opnSense i would setup failover multi-WAN and bridge them together so that one diyng will trigger the second one.

edit: fixed small errors