# Can never connect to repository after initial creation **URL:** \ **Category:** Support\ **Created:** [January 15, 2024, 3:44pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576 "2024-01-15T15:44:03Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![mrtorrent](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/mrtorrent/32/900_2.png) [@mrtorrent](https://kopia.discourse.group/u/mrtorrent)\ **Post date:** [January 15, 2024, 3:44pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/1 "2024-01-15T15:44:03Z")
I’m attempting to use KopiaUI to back up to an ExFAT-formatted USB drive. When I create the repository and use it during the same session, everything appears to work fine. However, any time I try to connect to the repository in the future - e.g. if I quit Kopia and re-open it, or unmount the drive and remount it - Kopia will not reconnect and gives an error like: > Connect Error: INTERNAL: internal server error: connect error: error opening repository: error connecting: unable to create shared content manager: error loading indexes: error downloading indexes: error loading index blob xn0\_d9.\_eca6c24b8f716d1d25ea3f86248bf5-s838d5d2a4969dda5124-c1: decrypt blob: unable to get index blob IV: invalid blob ID: xn0\_d9.\_eca6c24b8f716d1d25ea3f86248bf5 I have tried wiping the drive and creating a new repository multiple times, always with the same result. I’m using Kopia UI 0.15.0 on MacOS 13.6.3. Does anyone have any idea what the issue could be? ---
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [January 15, 2024, 3:54pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/2 "2024-01-15T15:54:33Z")
You can try to validate the provider (filesystem) first to check if there are any errors. > **[repository validate-provider](https://kopia.io/docs/reference/command-line/common/repository-validate-provider/)** > > $ kopia repository validate-provider Validates that a repository provider is compatible with Kopia > Flag Short Default Help --concurrency-test-duration Duration of concurrency test --get-blob-workers Number of GetBlob workers --get-metadata-workers... Cheers, ---
**Author:** ![mrtorrent](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/mrtorrent/32/900_2.png) [@mrtorrent](https://kopia.discourse.group/u/mrtorrent)\ **Post date:** [January 15, 2024, 4:09pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/3 "2024-01-15T16:09:33Z")
Thanks Chris. If I run validate-provider, I get the exact same error I posted above. ---
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [January 15, 2024, 4:29pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/4 "2024-01-15T16:29:25Z")
Than there might be something with the device. Can you check your HDD or USB drive? ---
**Author:** ![mrtorrent](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/mrtorrent/32/900_2.png) [@mrtorrent](https://kopia.discourse.group/u/mrtorrent)\ **Post date:** [January 15, 2024, 4:46pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/5 "2024-01-15T16:46:17Z")
It’s a relatively new NVME SSD. I’ve erased and repartitioned it; I’ve tested copying hundreds of gigabytes to it; I’ve run First Aid in Disk Utility. No issues with any of that. ---
**Author:** ![mrtorrent](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/mrtorrent/32/900_2.png) [@mrtorrent](https://kopia.discourse.group/u/mrtorrent)\ **Post date:** [January 15, 2024, 4:49pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/6 "2024-01-15T16:49:17Z")
Also, on the drive, there is a file ./xn0/\_d9/eca6c24b8f716d1d25ea3f86248bf5-s838d5d2a4969dda5124-c1.f That seems to be the one Kopia is looking for, so I’m not sure why it’s having an issue. ---
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [January 15, 2024, 5:45pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/7 "2024-01-15T17:45:10Z")
Hey, Would you mind checking for files starting with underscores? I guess this is your problem, see > > > After updating to v0.13.0 from v0.13.0-rc1, Kopia throws the following error whi…le trying to connect to the repository. > > \`Connect Error: INTERNAL: internal server error: connect error: error opening repository: error connecting: unable to create shared content manager: error loading indexes: error downloading indexes: error loading index blob xn15\_f.\_022f18e6d28f59eb4bf1789720d1b75-s41669725541c852e11c-c1: decrypt blob: unable to get index blob IV: invalid blob ID: xn15\_f.\_022f18e6d28f59eb4bf1789720d1b75\` > > Before rebooting my machine, I had issues with backing up. Unfortunately, I did not get a snippet of this other error. ---
**Author:** ![mrtorrent](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/mrtorrent/32/900_2.png) [@mrtorrent](https://kopia.discourse.group/u/mrtorrent)\ **Post date:** [January 15, 2024, 6:02pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/8 "2024-01-15T18:02:17Z")
Wow, that was it, thank you. Running dot\_clean as suggested in the GitHub issue allows Kopia to connect to the repository no problem. Seems like Kopia needs a way to handle these files, since MacOS always creates them by default. ---
**Author:** ![ChrisA](https://avatars.discourse-cdn.com/v4/letter/c/b77776/32.png) [@ChrisA](https://kopia.discourse.group/u/ChrisA)\ **Post date:** [January 15, 2024, 6:31pm UTC](https://kopia.discourse.group/t/can-never-connect-to-repository-after-initial-creation/2576/9 "2024-01-15T18:31:35Z")
Yeah, we need to handle it. Hopefully, there are some people who would like to join and participate 🙂