Selfhosted

61425 readers

602 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Reverse Proxy: a single point of failure in my lab (lemmy.dbzer0.com)

submitted 7 months ago* (last edited 7 months ago) by thisisnotausername@lemmy.dbzer0.com to c/selfhosted@lemmy.world

22 comments fedilink hide all child comments

So, just for the sake of it I've been trying to get my lab to be HA -or as HA as a small homelab can be-

My current set up is a follows:

3 proxmox servers with some Debian VMs, the VMs run docker swarm

A NAS, with Truenas

ISProuter -> OpenWRTRouter -> VM [Port fowards 80/443]

This works like a charm when I am in my LAN, but when I access from outside, if the VM that has 80/443 port forwarded to is down (which it never is) I'd loose connectivity.

I have now idea how to solve this little problem in a efficient way, maybe a reverse proxy running on my OpenWRT? (Which'd only move the point of failure to my router, but if my router goes down is gameover already anyways) has anyone attempted this?

Any opinions/ideas?

Update:

Solved! I moved my traefik data to a NFS share in my NAS, replicated the container across all manager nodes and then installed keepalived and now float a VIP between them.

Works like a charm and it was super easy to set up, literally 3 ansible tasks and 1 jinja template and you are done.

Thanks to all of ya!

you are viewing a single comment's thread
view the rest of the comments

[–] czl@lemmy.dbzer0.com 2 points 7 months ago* (last edited 7 months ago) (1 children)

My setup is a bit different, but maybe you can reuse part of it. Instead of using swarm for HA, I’m using proxmox. The LXCs have a failover to other machine (if they go down), and a static IP address, so if the http proxy machine goes down, it boots back up in another machine, with the same IP (and thus a working port forward).

This does mean that I have to keep the configuration in sync between different machines so my RPO is never too big, but for something like NPM where the config rarely changes, this isn’t much of an issue.

[–] thisisnotausername@lemmy.dbzer0.com 1 points 7 months ago

Super, thanks. I will look into this. I actually have some shared storage on my NAS for traefik configs which is already working on replicated instances.