TerraMaster Forum

rpc error: code = Code(101005) desc = connection deleted by admin

task stopped with error context canceled

terrasync/pkg/cfapi.UnRegisterCloudProvider

ciccioubiondin wrote: ↑15 Jan 2026, 01:31 Hello,
I’m experiencing a reproducible issue with TNAS PC / TerraSync 5.2.506 on Windows, using LAN only (no cloud, no TerraMaster ID).

Scenario:

- TerraMaster NAS on local network

- Two different Windows PCs

- Two different NAS users

- Sync configured via NAS local IP only

- No cloud login, no remote access

Problem:

When the second PC connects, the first one is immediately disconnected.
Sync tasks stop even though credentials, permissions, and network are correct.

Error line from TerraSync log

This line appears consistently at the moment the other PC connects:

rpc error: code = Code(101005) desc = connection deleted by admin

Followed by:

task stopped with error context canceled

Observations

This is not a network error or authentication failure

The NAS is actively terminating the connection

It happens only when another PC connects to the same NAS

The log also shows CFAPI / Cloud Provider calls even in LAN mode:

terrasync/pkg/cfapi.UnRegisterCloudProvider

This suggests that TNAS PC 5.2.506 may be:

treating multiple PCs as the same client (client_id collision)

enforcing a single active session even in LAN-only usage

Question

Is this a known issue in the 5.2.x branch?
Is there a way to:

allow multiple LAN clients simultaneously, or

disable Cloud/CFAPI behavior completely in LAN mode?

If needed, I can provide full logs.

Thank you.

• assigning completely different sync root folders on each PC

• deleting all existing TerraSync config/cache data before reconnecting

• testing with one PC on an older TNAS PC version to see if it’s specific to 5.2.506

williamcorlin wrote: ↑21 May 2026, 18:37

williamcorlin wrote: ↑21 May 2026, 18:37

ciccioubiondin wrote: ↑15 Jan 2026, 01:31

I’ve seen similar behavior on 5.2.x where a second TerraSync client caused the first session to drop unexpectedly, although in my case it was intermittent. Your theory about a client/session collision honestly sounds plausible, especially since the disconnect is so immediate and reproducible.
nulls brawl
The CFAPI entries are interesting too. It does seem like the Windows cloud provider layer is still involved even in pure LAN mode. You could try:

• assigning completely different sync root folders on each PC

• deleting all existing TerraSync config/cache data before reconnecting

• testing with one PC on an older TNAS PC version to see if it’s specific to 5.2.506

I don’t think multiple LAN clients are supposed to be restricted, so this feels more like a bug than intended behavior.

Aditiya wrote: ↑23 May 2026, 17:16

• Are you experiencing the exact same Code 101005 disconnection error under the same circumstances?

• What are the specific version numbers of the TNAS-PC and TerraSync you are currently running?