# New Client failed to initialize: error getting cached content, blob not found **URL:** \ **Category:** Support\ **Created:** [March 7, 2023, 5:56am UTC](https://kopia.discourse.group/t/new-client-failed-to-initialize-error-getting-cached-content-blob-not-found/1851 "2023-03-07T05:56:23Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [March 7, 2023, 5:56am UTC](https://kopia.discourse.group/t/new-client-failed-to-initialize-error-getting-cached-content-blob-not-found/1851/1 "2023-03-07T05:56:23Z")
Hi, since a few days, I am using kopia to backup my files and data. I am running a kopia docker container on a synology nas to backup my shares periodically. The same repository is used by two clients connecting to the repo via smb shares. I really appreciate the work of the developers as the software and the underlying data structure is quite fascinating. To my actual problem: Yesterday I tried to add a third client but it failed to initialize the repository. The message was: Connect Error: INTERNAL: internal server error: connect error: error connecting to repository: unable to list sources: unable to find manifest entries: unable to load manifest contents: error loading manifest content: error getting cached content: failed to get blob with ID… Maintenance is running fine: docker exec -it kopia /usr/bin/kopia --config-file=/app/config/repository.config maintenance info Owner: … Quick Cycle: scheduled: true interval: 1h0m0s next run: 2023-03-07 06:12:41 UTC (in 48m32s) Full Cycle: scheduled: true interval: 24h0m0s next run: 2023-03-07 17:26:09 UTC (in 12h2m0s) Log Retention: max count: 10000 max age of logs: 720h0m0s max total size: 1 GiB Recent Maintenance Runs: full-drop-deleted-content: 2023-03-06 17:26:53 UTC (2s) SUCCESS 2023-03-05 13:00:20 UTC (1s) SUCCESS 2023-03-04 12:26:09 UTC (2s) SUCCESS 2023-03-03 10:35:19 UTC (0s) SUCCESS 2023-03-02 10:25:50 UTC (1s) SUCCESS full-rewrite-contents: 2023-03-05 12:59:46 UTC (33s) SUCCESS 2023-03-03 10:33:25 UTC (1m54s) SUCCESS 2023-03-01 05:29:17 UTC (1s) SUCCESS snapshot-gc: 2023-03-06 17:26:10 UTC (43s) SUCCESS 2023-03-05 12:59:16 UTC (29s) SUCCESS 2023-03-04 12:25:40 UTC (28s) SUCCESS 2023-03-03 10:32:55 UTC (29s) SUCCESS 2023-03-02 10:25:33 UTC (16s) SUCCESS cleanup-epoch-manager: 2023-03-06 17:28:32 UTC (8s) SUCCESS 2023-03-05 13:00:22 UTC (5s) SUCCESS 2023-03-04 12:27:28 UTC (3s) SUCCESS 2023-03-03 10:35:20 UTC (1s) SUCCESS 2023-03-02 10:26:33 UTC (2s) SUCCESS cleanup-logs: 2023-03-06 17:28:32 UTC (0s) SUCCESS 2023-03-05 13:00:22 UTC (0s) SUCCESS 2023-03-04 12:27:28 UTC (0s) SUCCESS 2023-03-03 10:35:20 UTC (0s) SUCCESS 2023-03-02 10:26:33 UTC (0s) SUCCESS full-delete-blobs: 2023-03-06 17:26:56 UTC (1m36s) SUCCESS 2023-03-04 12:26:11 UTC (1m16s) SUCCESS 2023-03-02 10:25:52 UTC (41s) SUCCESS I am also able to connect to the repo just fine - using the other clients. What is strange is, that it is a new client never connected to the repository. I am currently verifying the whole repository using ` snapshot verify --verify-files-percent=100 --file-parallelism=10 --parallel=10` Any ideas what might be wrong? Cheers, Chris ---
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [March 9, 2023, 2:58pm UTC](https://kopia.discourse.group/t/new-client-failed-to-initialize-error-getting-cached-content-blob-not-found/1851/2 "2023-03-09T14:58:10Z")
Can be closed. Its a duplicate of [Unable to add a new client to an existing repository: Asks for blob which it never created - Support - Kopia Forum](https://kopia.discourse.group/t/unable-to-add-a-new-client-to-an-existing-repository-asks-for-blob-which-it-never-created/1857)