What your after is DNS fail over or round robin, round robin would be my option as both sites could be independent
this post was submitted on 10 Nov 2024
34 points (100.0% liked)
Selfhosted
40360 readers
325 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:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
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.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
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 1 year ago
MODERATORS
This is the correct answer. Healthcheck for each host to remove a dead endpoint from rotation.
Edit: missed your comment about static site
Unified state shouldn't be much of a problem for static web hosting.
OP said that they have a static website, this eliminates the need for session sync.
Thank you ! I'll look into it
Your challenge is that you need a loadbalancer. By hosting the loadbalancer yourself (e.g. on a VPS), you could also host your websites directly there...
My approach would be DNS-based. You can have multiple DNS A records, and the client picks one of them. With a little script you could remove one of the A Records of that server goes down. This way, you wouldn't need a central hardware.
That's an interesting idea, need to check if they offer some kind of a API for that.
But then there is this other thing, what about dns cache?
Set the DNS cache time to 60 seconds.
Set the script to run on every host delayed by some time to avoid simultaneously accessing the API (e.g. run the script every other minute).
With this approach, you get automatic failover in at most 3 minutes.
The VPS remains this single point of failure :(
The DNS-based approach seems to be the best bet for my use case.
Where would you host the script? If it's expected that the server that fires it off is always online and performing health checks, why not have it host a load-balancer? Or another local instance of the website? It's something fun to play around with, but if this is for anything beyond a fun exercise there are much better ways to accomplish this.
I'd host it on both webservers. The script sets the A record to all the servers that are online. Obviously, the script als has to check it's own service.
It seems a little hacky though, for a business use case I would use another approach.
If you don't want to mess with another VPS you can use a global server load balancer (GSLB) provider like Akamai, Cloudflare, Azure, etc.
This being a self-host community though it's unlikely you'd want to pursue something like this, but without knowing more about your specific use case it's tough to make a recommendation.
If global high-availability is your primary goal then a hosted solution is probably best.
If this is just an exercise you and your friend are working on for giggles and it's not for a mission-critical Production instance, then presumably self-hosting a load-balancer on each of your servers that includes both nodes in a target group would achieve this, though somewhat counterintuitive; if the website goes down at either location, I would imagine there's a pretty high likelihood the LB itself would be down as well.
Essentially you need a load balancer hosted somewhere that the traffic hits before getting routed to one of the 2 servers. That could be a VPS running Traefik if you prefer that.
Alternatively you could both run something like IPFS and run the static site on that, but anyone accessing the site would either need IPFS installed, or use a gateway hosted somewhere (Cloudflare has a public for example).
I think what you're looking for is what is sometimes called a "dns load balancer". Offerings like Azure Traffic Manager or AWS Route 53 do this. You can set up health checks that the service will use to determine if one of your locations is down and then automatically update the DNS record to point to the other one. You can also get clever and do things that allow the DNS to resolve the IP of whichever of your servers is physically closer so you get the best performance. I'm not sure what options there are for selfhosting a DNS service like this, however, these services are extremely affordable -- pennies -- and run on very reliable infrastructure, which is what you want.
Oh nice ! I will check that
Many moons ago I used heartbeat for this, but you’d need both servers in the same cidr range. I assume that’s not the case here.
In your case you could probably use a dynamic DNS service to move the IP around, but the challenge would be knowing when to kick it off.
You could write scripts to determine when the live one goes down, but we’re probably already more complicated than you were looking for.