Support for Docker image nebula-sync

 

Application Name: nebula-sync

Application Site: https://github.com/lovelaze/nebula-sync
Application repository:  https://github.com/lovelaze/nebula-sync

Overview:  Synchronize Pi-hole v6.x configuration to replicas.

This project is not a part of the official Pi-hole project, but uses the api provided by Pi-hole instances to perform the synchronization actions.

Features
* Full sync: Use Pi-hole Teleporter for full synchronization.
* Manual sync: Selective feature synchronization.
* Cron schedule: Run on chron schedule.

*** REQUIRE PI-HOLE V6 ***
Reminder Pihole V6 is still under heavy development

 

 

Make sure to look at the complete documentation

 

Please post any questions/issues relating to this docker template you have in this thread.

reserved

Not sure if this thread is still active but I've tried hunting around but the github page has very lack luster setup instructions for unraid and I'm not super well versed in docker. So far I'm not sure what IP address I need to put in. If it needs to have /admin or :443 or :80 for use HTTPS or HTTP or /api at the end. My password is just a string of numbers as well so no fancy characters. I use a pihole app and I can access my pi's just fine using HTTPS. I also tried swapping the ports to 80 and http

I am currently getting this error. 

2025-02-28T23:38:56+11:00 INF Starting nebula-sync v0.3.0
2025-02-28T23:38:56+11:00 INF Running full sync replicas=1
2025-02-28T23:38:56+11:00 INF Authenticating clients...
2025-02-28T23:38:56+11:00 FTL Sync failed error="authenticate: https://192.168.1.8:443/api/auth: Post \"https://192.168.1.8:443/api/auth\": tls: failed to verify certificate: x509: cannot validate certificate for 192.168.1.8 because it doesn't contain any IP SANs"

If I try HTTP I get this error:

2025-02-28T23:42:55+11:00 INF Starting nebula-sync v0.3.0
2025-02-28T23:42:55+11:00 INF Running full sync replicas=1
2025-02-28T23:42:55+11:00 INF Authenticating clients...
2025-02-28T23:42:55+11:00 FTL Sync failed error="authenticate: http://192.168.1.8:80/api/auth: Post \"http://192.168.1.8:80/api/auth\": dial tcp 192.168.1.8:80: connect: connection refused"

** Press ANY KEY to close this window **

On 2/28/2025 at 12:43 PM, widowshyper said:

Not sure if this thread is still active but I've tried hunting around but the github page has very lack luster setup instructions for unraid and I'm not super well versed in docker. So far I'm not sure what IP address I need to put in. If it needs to have /admin or :443 or :80 for use HTTPS or HTTP or /api at the end. My password is just a string of numbers as well so no fancy characters. I use a pihole app and I can access my pi's just fine using HTTPS. I also tried swapping the ports to 80 and http

I am currently getting this error. 

2025-02-28T23:38:56+11:00 INF Starting nebula-sync v0.3.0
2025-02-28T23:38:56+11:00 INF Running full sync replicas=1
2025-02-28T23:38:56+11:00 INF Authenticating clients...
2025-02-28T23:38:56+11:00 FTL Sync failed error="authenticate: https://192.168.1.8:443/api/auth: Post \"https://192.168.1.8:443/api/auth\": tls: failed to verify certificate: x509: cannot validate certificate for 192.168.1.8 because it doesn't contain any IP SANs"

If I try HTTP I get this error:

2025-02-28T23:42:55+11:00 INF Starting nebula-sync v0.3.0
2025-02-28T23:42:55+11:00 INF Running full sync replicas=1
2025-02-28T23:42:55+11:00 INF Authenticating clients...
2025-02-28T23:42:55+11:00 FTL Sync failed error="authenticate: http://192.168.1.8:80/api/auth: Post \"http://192.168.1.8:80/api/auth\": dial tcp 192.168.1.8:80: connect: connection refused"

** Press ANY KEY to close this window **

Hey widowshyper, I'm getting the same error message, did you find a solution?

 

I have pihole running on hardware for my main instance and then my backup instance is running on unraid with its own ip address. But getting the sames errors as yourself if using http or https.

wow i did not get notification.... for widowshyper message 
luckily got one for yours

make sure you are running pi-hole v6 Please 
that's said can you try 
that said i need to know how you access pihole web ui ?
i mean on which port ?

 

also for your HTTPS issue, you probably need :
 

CLIENT_SKIP_TLS_VERIFICATION=true

 

Edited March 21, 20251 yr by ZappyZap

I am having the same problems and the CLIENT_SKIP_TLS_VERIFICATION=true didn't help. following this thread. 

I want to do a partial sync. Docker in unRAID is not intuitive. How do you add the variables for the sync options?

Thanks!

On 3/23/2025 at 10:00 AM, av8rdude said:

I want to do a partial sync. Docker in unRAID is not intuitive. How do you add the variables for the sync options?

Thanks!

add each variable manually as part of the docker settings (see attached). I kept the name the same as the key for consistency, but the key is the actual variable name. 

 

also make sure nebula and pihole are on the same docker network. That bit me. 

 

 

yes that's one way.

I would love to learn other ways to add variables. Unfortunately most documentation assumes that one already knows how to do everything. 

Docker worked perfectly for me - thanks.

Docker worked perfecty for me as well.

Default sync settings.  2 replicas using http not https. 

Thanks!

So this will only work if the DNS pi-hole is on the same network as the Docker?

Also how do I see the logs? or anything? I did a setup and it is running but I do not see any errors or any feedback in /various/log and no changes or updates on the primary nor secondary pihole.

and yes my pi-holes are on a different network.

Gee, make my first post in a while then I find the solution. Nope DNS pi-hole doe snot need to be on the same network. Just need the right route and port. TLS had to be disabled and the right port, might be one of these: 80, 8080, 443, 8443, etc

BTW to review logs do this:

docker logs -f nebula-sync

this is how I found my errors

FYI for sanity I did this:

1) to prove container exists: docker ps -a --format "table {{.Names}}\t{{.Image}}\t{{.Status}}" | grep -i nebula

2) Confirm it is running: docker ps --format "table {{.Names}}\t{{.Status}}\t{{.Ports}}" | grep -i nebula

3) Check logs to confirm: docker logs --tail 200 nebula-sync