only one pihole syncs

[hspindel]

What happened?

Doubt that this is a bug, more likely a misconfiguration on my part.

I have three piholes, one Primary and two Replicas. One of the Replicas gets synced, the other does not.

If I run nebula sync, it reports:
Starting v0.11.1
Authenticating clients
Syncing teleporters
Syncing configs
Running gravity
Invalidating sessions
Sync complete

So no complaints from nebula sync. I've tried enabling debug, but neither LOG_LEVEL=debug nor DEBUG=true in my environment file do anything.

I am running nebula sync as a binary under Debian. Debian is a VM under Proxmox. No docker involved.

How do I figure out what's going wrong?

Expected Behaviour

I expect both REPLICA piholes to sync.

Nebula-sync Version

0.11.1

Runtime

binary

Operating System

Debian Gnu/Linux 13 (Trixie)

CPU Architecture

6.12.744+deb13+1-amd64

Configuration

PRIMARY=http://pi1.mydomain.com|password
REPLICAS=http://pi2.mydomain.com|password
REPLICAS=http://pi3.mydomain.com|password
FULL_SYNC=true
RUN_GRAVITY=true

In the above config, it's the first replica that doesn't get synced.

Relevant log output

I can't find any relevant logs.  Please tell me what you need.

Pi-hole Version

Core 6.4.2 FTL 6.6.1 Web Interface 6.5

[catanbri]

You do have a configuration issue. The replicas line should contain all replicas comma separated.
REPLICAS=http://pi2.mydomain.com|password,http://pi3.mydomain.com|password
The environment variable you need for debug logs would be NS_DEBUG=TRUE.

[hspindel]

You do have a configuration issue. The replicas line should contain all replicas comma separated. REPLICAS=http://pi2.mydomain.com|password,http://pi3.mydomain.com|password The environment variable you need for debug logs would be NS_DEBUG=TRUE.

Very cool, thank you for correcting my config file, and the piholes are syncing now.

I did discover that if I left a space between the two piholes on the REPLICAS line (after the comma), it failed. It's unexpected that white space would make a difference.

Also, I've discovered that after running the sync, the REPLICA piholes are inaccessible on their web page for a little while (at least several seconds). Is this normal and is there a way to reduce the time the piholes are inaccessible?

Adding NS_DEBUG=true to the environment file didn't result in any additional output. Maybe because it worked? Or does the debug switch go somewhere else?

PRIMARY=http://rasp-pihole6.sci1.com|sleuthy
REPLICAS=http://pihole1.mydomain.com|passworx,http://pihole2.mydomain.com|password
FULL_SYNC=true
RUN_GRAVITY=true
NS_DEBUG=true

Thank you very much for helping me get this to work!

[catanbri]

If you successfully set the NS_DEBUG variable you will start to see DBG messages in your docker logs nebula-sync
2026-04-27T17:22:57-05:00 INF github.com/lovelaze/nebula-sync/internal/service/service.go:66 > Starting nebula-sync v0.11.1 2026-04-27T17:22:57-05:00 DBG github.com/lovelaze/nebula-sync/internal/api/server.go:38 > Starting http server 2026-04-27T17:22:57-05:00 DBG github.com/lovelaze/nebula-sync/internal/service/service.go:67 > Settings config= 2026-04-27T17:22:57-05:00 INF github.com/lovelaze/nebula-sync/internal/sync/sync.go:35 > Running sync mode=full replicas=2 2026-04-27T17:22:57-05:00 INF github.com/lovelaze/nebula-sync/internal/sync/sync.go:52 > Authenticating clients... 2026-04-27T17:22:57-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:66 > PostAuth client= 2026-04-27T17:22:57-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:66 > PostAuth client= 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:66 > PostAuth client= 2026-04-27T17:22:58-05:00 INF github.com/lovelaze/nebula-sync/internal/sync/sync.go:84 > Syncing teleporters... 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:149 > Get teleporter client= 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:175 > Post teleporter client= 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:175 > Post teleporter client= 2026-04-27T17:22:58-05:00 INF github.com/lovelaze/nebula-sync/internal/sync/sync.go:107 > Syncing configs... 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:226 > Get config client= 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:261 > Patch config client= 2026-04-27T17:22:58-05:00 DBG github.com/lovelaze/nebula-sync/internal/pihole/client.go:261 > Patch config client=

But this is about as far as I can go on help. I dont understand GOlang well enough to comment on the whitespace issue

[hspindel]

I don't use Docker, so there are no Docker logs. No longer terribly important since it's working.