Troubleshooting

Device is not enrolled

If c3sync status shows enrolled false, repeat c3sync login and verify the hub URL, TLS PIN, enrollment credentials, and master passphrase. An enrolled responder must be online during the PAKE exchange.

Sessions do not appear

Run c3sync daemon status on both peers and inspect daemon logs for handler failures. Verify the agent is supported and the session directory is accessible to the daemon service account.

Files do not move

Confirm both clones represent the same project identity.
Check .gitignore, .c3syncignore, and .c3syncinclude.
Run c3sync sync to bypass the capture debounce.
Check status for a bulk-deletion hold or unresolved conflict.

One peer always wins

Check the machine clocks. Hybrid logical clocks protect ordering, but a device with a far-future wall clock is logged and can bias conflict resolution until corrected.

Concurrent session warning

Stop one of the two agents writing to the same native session, then materialize again. Sequential continuation across machines is supported; simultaneous writers to one session are not.