# Can not connect to repository (local storage smb mount)

**URL:** <https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818>\
**Category:** Support\
**Created:** [December 18, 2021, 6:14pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818 "2021-12-18T18:14:18Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Torsten](https://avatars.discourse-cdn.com/v4/letter/t/8e8cbc/32.png) [@Torsten](https://kopia.discourse.group/u/Torsten)\
**Post date:** [December 18, 2021, 6:14pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/1 "2021-12-18T18:14:18Z")

</div>

Hi, I installed Kopia on my iMac a few days ago and created a repository on a local storage (smb mount NAS). After that I created several snapshots from different folders. I have also connected a Linux client to the repository which also makes snapshots.  
Today the Mac did not connect to the repository anymore and I could not connect to the repository although the repository password is correct. I tried to connect via Kopia-ui and even via the terminal

```auto
Connect Error: INTERNAL: internal server error: connect error: unable to create shared content manager: error loading indexes: error downloading indexes: error loading index blob xn4_afc9d88531a2fb9566b2cfc8e98602f2-s398f8f9a69deeb8110b-c1: error decrypting BLOB xn4_afc9d88531a2fb9566b2cfc8e98602f2-s398f8f9a69deeb8110b-c1: unable to decrypt content: cipher: message authentication failed

```

The Linux client can still connect to the repository and takes snapshots.

---

<div class="post-metadata">

**Author:** ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)\
**Post date:** [December 18, 2021, 6:41pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/2 "2021-12-18T18:41:27Z")

</div>

You have some data corruption - previous instances of this usually indicated faulty RAM or some problem with the underlying hard disk.

You can try deleting the offending index file, you will lose all writes done in that session, but there’s a reasonably high chance that the rest of the repository won’t be affected.

---

<div class="post-metadata">

**Author:** ![Torsten](https://avatars.discourse-cdn.com/v4/letter/t/8e8cbc/32.png) [@Torsten](https://kopia.discourse.group/u/Torsten)\
**Post date:** [December 18, 2021, 6:50pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/3 "2021-12-18T18:50:14Z")

</div>

Okay, can you tell me where I find the offending index file?

you mean this one? xn4\_afc9d88531a2fb9566b2cfc8e98602f2-s398f8f9a69deeb8110b-c1

---

<div class="post-metadata">

**Author:** ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)\
**Post date:** [December 18, 2021, 7:23pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/4 "2021-12-18T19:23:54Z")

</div>

yes, it’s in the repository subdirectory `/x/n4_`

---

<div class="post-metadata">

**Author:** ![Torsten](https://avatars.discourse-cdn.com/v4/letter/t/8e8cbc/32.png) [@Torsten](https://kopia.discourse.group/u/Torsten)\
**Post date:** [December 18, 2021, 7:41pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/5 "2021-12-18T19:41:00Z")

</div>

Okay i have delete the file and then I was able to open the repository.

---

<div class="post-metadata">

**Author:** ![jkowalski](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/jkowalski/32/3_2.png) [@jkowalski](https://kopia.discourse.group/u/jkowalski)\
**Post date:** [December 18, 2021, 9:20pm UTC](https://kopia.discourse.group/t/can-not-connect-to-repository-local-storage-smb-mount/818/6 "2021-12-18T21:20:57Z")

</div>

Definitely check your RAM for bad bits and HDD for bad sectors.
