Is your feature request related to a problem? Please describe.
I updated two of my 3x Pi-Holes, and I was getting some error that didn't fully describe the fault, it took me some effort to try to find the solution, since the error wasn't descriptive enough, and Nebula-Sync would crash during startup so I was hesitant to update the third instance.
# Error I was receiving
nebulasync-c1 | 2025-12-13T12:28:19Z FTL github.com/lovelaze/nebula-sync/cmd/run.go:25 > Sync failed error="sync configs: https://10.x.y.53/api/config: Patch \"https://10.x.y.53/api/config\": dial tcp 10.x.y.53:443: connect: connection refused"
Describe the solution you'd like
If Nebula-Sync is able to connect to the out-of-date instance and describe the failure with more context, it would help point to the real problem. Since Nebula-Sync was working for months until I updated the Primary instance, I was focused on where I made my changes, not the Pi-Hole Instance that I had purposefully left un-updated. It led me down the wrong path.
# Example error I would like to receive
nebulasync-c1 | 2025-12-13T12:28:19Z FTL github.com/lovelaze/nebula-sync/cmd/run.go:25 > Sync failed error="sync configs: https://10.x.y.53/api/config: Patch \"https://10.x.y.53/api/config\": dial tcp 10.x.y.53:443: connect: connection refused"
nebulasync-c1 | 2025-12-13T12:28:19Z FTL github.com/lovelaze/nebula-sync/cmd/run.go:25 > Sync failed error: 10.x.y.53 FTL version does not match Primary.
Describe alternatives you've considered
Alternatively, allowing Nebula-Sync to start even when one of the replicas is not being updated, with error during update would be useful. Post an error when the sync fails for the instance that fails.
Anything else?
No response
Is your feature request related to a problem? Please describe.
I updated two of my 3x Pi-Holes, and I was getting some error that didn't fully describe the fault, it took me some effort to try to find the solution, since the error wasn't descriptive enough, and Nebula-Sync would crash during startup so I was hesitant to update the third instance.
Describe the solution you'd like
If Nebula-Sync is able to connect to the out-of-date instance and describe the failure with more context, it would help point to the real problem. Since Nebula-Sync was working for months until I updated the Primary instance, I was focused on where I made my changes, not the Pi-Hole Instance that I had purposefully left un-updated. It led me down the wrong path.
Describe alternatives you've considered
Alternatively, allowing Nebula-Sync to start even when one of the replicas is not being updated, with error during update would be useful. Post an error when the sync fails for the instance that fails.
Anything else?
No response