only v0.5.0 completes correctly

[snuzs]

I have 2 pi-hole v6 running and v0.5.0 of nebula-sync appears to be working correctly.
2025-05-17T10:46:39-05:00 INF Starting nebula-sync v0.5.0
2025-05-17T10:46:39-05:00 INF Running full sync replicas=1
2025-05-17T10:46:39-05:00 INF Authenticating clients...
2025-05-17T10:46:40-05:00 INF Syncing Teleporters...
2025-05-17T10:46:40-05:00 INF Running gravity...
2025-05-17T10:46:40-05:00 INF Invalidating sessions...
2025-05-17T10:46:40-05:00 INF Sync complete

When I try v0.11.0, it fails with the error message below. This same failure was seen with every version between v0.6.0 - v0.10.0 as well.
2025-05-17T10:45:31-05:00 INF Starting nebula-sync v0.11.0
2025-05-17T10:45:31-05:00 INF Running sync mode=full replicas=1
2025-05-17T10:45:31-05:00 INF Authenticating clients...
2025-05-17T10:45:32-05:00 INF Syncing teleporters...
2025-05-17T10:45:32-05:00 INF Syncing configs...
2025-05-17T10:45:36-05:00 INF Invalidating sessions...
2025-05-17T10:45:36-05:00 FTL Sync failed error="sync configs: https://192.168.2.4/api/config: unexpected status code: 400"

Here is my docker config:
version: '3'

services:
nebula-sync:
image: ghcr.io/lovelaze/nebula-sync:v0.11.0
container_name: nebulasync
hostname: nebulasync
environment:
#NS_DEBUG: true
PRIMARY: 'https://192.168.2.3|’
REPLICAS: 'https://192.168.2.4|’
FULL_SYNC: true
RUN_GRAVITY: true
CRON: '0 * * * *'
TZ: 'America/Chicago'
CLIENT_SKIP_TLS_VERIFICATION: true

When I've tried turning debugging on, I don't really get anything additional than "unexpected status code: 400"

v0.5.0 appears to sync things correctly (I've tried changing settings on one to see that they get replicated on the second)

I'm out of ideas. Any thoughts? Thanks!

[lovelaze]

Hi @snuzs

This is most likely exactly the same as #147, please check this comment there

[snuzs]

Thank you - that appears to have been the issue - seems to be running correctly now on v0.11.0