You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to start by saying thank you for putting this together - it's been working great!
As the title states, would it be possible to add a second instance of this for automatic failover redundancy? For example, I have the networking stack set up on Server 1, and it goes down. Is it possible for clients to automatically switch to Server 2?
I'm not sure how well this would work because if I add Server 2 as a client to Server 1's WireGuard, then if it goes down, I can't use Server 2's PiHole instance anyway.
I suppose a simple method would be to have Server 1 and Server 2 as separate configurations in the WireGuard client, but it would be neat to have an automatic failover.
I'm not well versed in networking, and I appreciate any input! (even if it's a "no, this can't be done")
The text was updated successfully, but these errors were encountered:
JoshLoecker
changed the title
Setting up second PiHole/WireGuard server for failover/redundancy
Setting up second WireHole server for failover/redundancy
Jan 19, 2022
I'd like to start by saying thank you for putting this together - it's been working great!
As the title states, would it be possible to add a second instance of this for automatic failover redundancy? For example, I have the networking stack set up on Server 1, and it goes down. Is it possible for clients to automatically switch to Server 2?
I'm not sure how well this would work because if I add Server 2 as a client to Server 1's WireGuard, then if it goes down, I can't use Server 2's PiHole instance anyway.
I suppose a simple method would be to have Server 1 and Server 2 as separate configurations in the WireGuard client, but it would be neat to have an automatic failover.
I'm not well versed in networking, and I appreciate any input! (even if it's a "no, this can't be done")
The text was updated successfully, but these errors were encountered: