# Bug: v0.19.0: CLI/GUI/AppImage: repository.config Over-writes Without Warning **URL:** \ **Category:** Support\ **Created:** [April 24, 2025, 11:37pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899 "2025-04-24T23:37:25Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 24, 2025, 11:37pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/1 "2025-04-24T23:37:25Z")
_tags: das, direct attached storage, usb drive, usb disk, file system repo, webdav, dav, webdav repo, dav repo, multi repo, multiple repositories_ - I create a filesystem based repo to a USB attached volume. Result: - A basic set of Kopia files appear as expected in the target dir. - `$HOME/.config/kopia/repository.conf` shows a `"path:"` of the expected path. - I create another filesystem based repo to an internal disk/attached volume. Result: - A basic set of Kopia files appear as expected in the target dir. - Only _one_ `$HOME/.config/kopia/repository.conf` present. - This conf shows the `"path:"` of the _second_ volume. _There is no trace of the conf for the USB attached volume!_ Do these devs™ even lack the foresight to think people have **multiple** volumes/endpoints in/from their machines?! ```auto cat repository.config && nowutc ───────┬──────────────────────────────────────────────────────────────────────────────────────────────── │ File: repository.config ───────┼──────────────────────────────────────────────────────────────────────────────────────────────── 1 │ { 2 │ "storage": { 3 │ "type": "filesystem", 4 │ "config": { 5 │ "path": "/media/usb-disk/kopia/000", 6 │ "fileMode": 384, 7 │ "dirMode": 448, 8 │ "dirShards": null, 9 │ "listParallelism": 4 10 │ } 11 │ }, 12 │ "caching": { 13 │ "cacheDirectory": "../../.cache/kopia/c51079195f889780", 14 │ "maxCacheSize": 5242880000, 15 │ "maxMetadataCacheSize": 5242880000, 16 │ "maxListCacheDuration": 30 17 │ }, 18 │ "hostname": "hostname", 19 │ "username": "username", 20 │ "description": "Test Repository 000", 21 │ "enableActions": true, 22 │ "formatBlobCacheDuration": 900000000000 23 │ } ───────┴──────────────────────────────────────────────────────────────────────────────────────────────── 20250424T233005UTC ``` ```auto ───────┬──────────────────────────────────────────────────────────────────────────────────────────────── │ File: repository.config ───────┼──────────────────────────────────────────────────────────────────────────────────────────────── 1 │ { 2 │ "storage": { 3 │ "type": "filesystem", 4 │ "config": { 5 │ "path": "/mnt/volume/kopia/012", 6 │ "fileMode": 384, 7 │ "dirMode": 448, 8 │ "dirShards": null, 9 │ "listParallelism": 4 10 │ } 11 │ }, 12 │ "caching": { 13 │ "cacheDirectory": "../../.cache/kopia/c017f435748de612", 14 │ "maxCacheSize": 5242880000, 15 │ "maxMetadataCacheSize": 5242880000, 16 │ "maxListCacheDuration": 30 17 │ }, 18 │ "hostname": "hostname", 19 │ "username": "username", 20 │ "description": "Test Repository 012", 21 │ "enableActions": true, 22 │ "formatBlobCacheDuration": 900000000000 23 │ } ───────┴──────────────────────────────────────────────────────────────────────────────────────────────── 20250424T233037UTC ``` * * * > [@Disk full - Snapshot delete not possible !?](https://kopia.discourse.group/t/disk-full-snapshot-delete-not-possible/1759/2): > > Check [FR - Native way for kopia to recover from underlying storage running out of space · Issue #1738 · kopia/kopia · GitHub](https://github.com/kopia/kopia/issues/1738) > [@Help needed with snapshot verify](https://kopia.discourse.group/t/help-needed-with-snapshot-verify/3887/3): > > I have tried and indeed it does not work. Looks like a bug for me. > [@Bug: v0.19.0: CLI: Logs default to debug](https://kopia.discourse.group/t/bug-v0-19-0-cli-logs-default-to-debug/3824/1): > > Near 1000 lines written… plus ten (10) more multi-line, supposed log files and I haven’t even taken a snapshot. Almost ten years and this software still defaults to ‘debug.’ $HOME/.cache/kopia/cli-logs/kopia-20250320-064117-220796-server-start.0.log 2025-03-20T06:41:17.469576Z INFO kopia/cli Server will allow connections from users whose accounts are stored in the repository. User accounts can be added using 'kopia server user add'. 2025-03-20T06:41:17.472158Z INFO kopia/server Repository … > [@Bug: KopiaUI v0.19.0: Linux: Does not honor XDG Base Directory Specification](https://kopia.discourse.group/t/bug-kopiaui-v0-19-0-linux-does-not-honor-xdg-base-directory-specification/3818/1): > > tags: xdg, linux, xdg base dir, specs, specifications KopiaUI on Linux does not appear to honor the XDG Base Directory Specification. EG: $XDG\_CACHE\_HOME for kopai-ui’s Electron remnants ($HOME/.config/kopia-ui) line 13 of $HOME/.config/kopia/repository.config "cacheDirectory": "../../.cache/kopia/9110c879a34eee0a KopiaUI Version v0.19.0 1f8f728c4133d4f419df93e58a5b54c3bf9c75e3 kopia/htmlui 16dfe3793a020835bc6a98d75e7c2550210954e1 built on Sat Dec 28 09:10:28 UTC 2024 fv-az798-492 (appima… > [@Bug: KopiaUI v0.19.0: WebDAV: Cannot create repo nested in an existing collection/dir](https://kopia.discourse.group/t/bug-kopiaui-v0-19-0-webdav-cannot-create-repo-nested-in-an-existing-collection-dir/3819/1): > > tags: webdav, mkcol, dir, mkdir, directory, directories, collections, nested Kopia does not seem to utilize mkcol to create sub ‘directories’ under existing ‘paths.’ EG: https://$sub.$tld.internal:2443/dav/$usr/backup This does not create /backup on the endpoint. The ‘create repository’ button does nothing. The user has sufficient permissions to the root (eg: $usr/ exists but $usr/backup does not). The directory/collection must be manually created on the server/endpoint before creating the r… > [@Bug: KopiaUI v0.19.0: WebDAV: Unable to authenticate against SHA256 Digests/RFC 7616 (HTTP userhash extension)](https://kopia.discourse.group/t/bug-kopiaui-v0-19-0-webdav-unable-to-authenticate-against-sha256-digests-rfc-7616-http-userhash-extension/3817): > > tags: webdav, auth, authentication, digest, htdigest, realms, rfc-7616, rfc-2617, rfc-1945, sha2, sha256, hashing, salting, encryption, encrypting, user accounts, message-digest-algorithm, lighttpd, mod\_webdav, mod\_auth, mod\_authn\_file, auth.backend I’m unable to connect KopiaUI to a WebDAV target. The endpoint runs Lighttpd (1.4.69) using mod\_authn\_file htdigests. It is configured to use SHA256 hashing. It also uses RFC 7616’s HTTP Digest auth userhash extension.[1] Note RFC 7616 (2015) obsol… ---
**Author:** ![budy](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/budy/32/38_2.png) [@budy](https://kopia.discourse.group/u/budy)\ **Post date:** [April 25, 2025, 12:21pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/2 "2025-04-25T12:21:46Z")
All I can do is say, that this works for me. I have a Kopia repo on an external disc which is connected through USB-C (on my Mac) and the path stated in the config represents the location of the repo on this external volume: ```auto { "storage": { "type": "filesystem", "config": { "path": "/Volumes/BudysBackup/KopiaTest", "dirShards": null } }, "caching": { "cacheDirectory": "../../Caches/kopia/3450c22b1be32a14", "maxCacheSize": 5242880000, "maxMetadataCacheSize": 5242880000, "maxListCacheDuration": 30 }, "hostname": "xxxxxxxx", "username": "xxxxxxxx", "description": "KopiaTest", "enableActions": false, "formatBlobCacheDuration": 900000000000 } ``` I created that repo for testing purposes using Kopia 0.18 on macOS. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 25, 2025, 10:24pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/3 "2025-04-25T22:24:12Z")
Thanks for checking. Version, OS differences aside you’re able to successfully set multiple repos on your USB volume as something like `/Volumes/BudysBackup/{KopiaTest-00,KopiaTest-01}`, etc? Am I correct in presuming you’re doing this thru the CLI? I presume so. This may a misreport. I’ll retest when I get time later today. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 25, 2025, 10:44pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/4 "2025-04-25T22:44:21Z")
Confirmed 20250425T223922UTC: two repo attempts on one volume result in _one_ `$HOME/.config/repository.conf`: - `"description": "Test Repository 000",` with `"path": "/media/mnt7/kopia/000",` - `"description": "Test Repository 001",` with `"path": "/media/mnt7/kopia/001",` - `cacheDirectory`’s are different. I’m calling this a bug in v0.19.0 unless proven otherwise. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 25, 2025, 10:48pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/5 "2025-04-25T22:48:15Z")
Confirmed 20250425T224602UTC: two repo attempts on two volumes result in _one_ `$HOME/.config/repository.conf` : - `"description": "Test Repository 001",` with `"path": "/media/mnt7/kopia/001",` - `"description": "Test Repository 002",` with `"path": "/media/mnt12/kopia/002",` - `cacheDirectory`’s are different. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 25, 2025, 11:11pm UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/6 "2025-04-25T23:11:03Z")
I tell a lie: I’m using the CLI commands via the AppImage. ~~[That may be a distinction](https://github.com/kopia/kopia/blob/master/BUILD.md).~~ Title updated. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 26, 2025, 7:00am UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/7 "2025-04-26T07:00:14Z")
So I just connected a test repo to a WebDAV endpoint via the GUI. Now `$HOME/.config/repository.conf` shows `"url": "https:// [...]` & the credentials. `cacheDirectory` is, as expected, different. 20250426T065616UTC. Brilliant. Just brilliant. ---
**Author:** ![97b4958b055b](https://avatars.discourse-cdn.com/v4/letter/9/47e85d/32.png) [@97b4958b055b](https://kopia.discourse.group/u/97b4958b055b)\ **Post date:** [April 26, 2025, 7:04am UTC](https://kopia.discourse.group/t/bug-v0-19-0-cli-gui-appimage-repository-config-over-writes-without-warning/3899/8 "2025-04-26T07:04:45Z")
Unreal. Adding a sole file system repo via CLI after creating a WebDAV one _also_ overwrites `$HOME/.config/repository.conf`. 20250426T070144UTC. **NINE YEARS.**