# \[SOLVED\] Kopia ui no longer takes snapshots and I can't run Snapshot now

**URL:** <https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844>\
**Category:** Support\
**Created:** [April 1, 2026, 4:06am UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844 "2026-04-01T04:06:38Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![ieugen](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ieugen/32/467_2.png) [@ieugen](https://kopia.discourse.group/u/ieugen)\
**Post date:** [April 1, 2026, 4:06am UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844/1 "2026-04-01T04:06:38Z")

</div>

Hello,

About 2 months ago my kopia local setup broke and I don’t know what is wrong and how to fix it.

I can open my repo and I can see my snapshots but I can’t take more snapshots and I see an “overdue” in the “Next snapshot” column.

 ![image](https://global.discourse-cdn.com/free1/uploads/kopia/original/2X/a/a3869341b2b5a1ba6ecf21b0d1d95d42df8a0705.png)

I am using kopia 0.22.3 installed from GH releases and I have been updating on every release.

I don’t see anything in ~/.config/kopia-ui/logs/main.log .  
I am running on Debian 13 Trixie + testing

```auto
Package: kopia-ui
Version: 0.22.3
Priority: optional
Section: default
Maintainer: Kopia Authors <kopia-pmc@googlegroups.com>
Installed-Size: 348 MB
Depends: libgtk-3-0, libnotify4, libnss3, libxss1, libxtst6, xdg-utils, libatspi2.0-0, libuuid1, libsecret-1-0
Recommends: libappindicator3-1
Homepage: https://./
License: Apache-2.0
Vendor: Kopia Authors <kopia-pmc@googlegroups.com>
Download-Size: 91,1 MB
APT-Manual-Installed: yes
APT-Sources: http://packages.kopia.io/apt stable/main amd64 Packages
Description: Fast and secure open source backup.

```

---

<div class="post-metadata">

**Author:** ![ieugen](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ieugen/32/467_2.png) [@ieugen](https://kopia.discourse.group/u/ieugen)\
**Post date:** [April 1, 2026, 8:45am UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844/2 "2026-04-01T08:45:05Z")

</div>

I’ve noticed that my snapshots are not “local” they belong to a username and host (me and the name of my system).  
Don’t know if this has any impact.

Trying a manual snapshot give me “no snapshot sources”, even though I do have snapthots but they are marked as snapshots for “user@host” and not “Local snapshots” .

```auto
/opt/KopiaUI/resources/server/kopia --config-file=$HOME/.config/kopia/repository.config snapshot create --all
no snapshot sources

```

---

<div class="post-metadata">

**Author:** ![ieugen](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ieugen/32/467_2.png) [@ieugen](https://kopia.discourse.group/u/ieugen)\
**Post date:** [April 1, 2026, 10:44am UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844/3 "2026-04-01T10:44:10Z")

</div>

I have found the issue and the solution.

In my case, there was an small - 1 character typo - in the owner hostname for the snapshots.

For some reason, my current user@host that I was connecting to the repo was 1 character different from the owner of the snapshots.

I don’t know how this happened and I missed it for quite some time (names where very similar, and I often used both).

I noticed this after I manually created a snapshot. I saw the difference in hostname and the new snapshot had the “Take snapshot” button.

```auto
# manually create snapshot for a directory
/opt/KopiaUI/resources/server/kopia --config-file=$HOME/.config/kopia/repository.config snapshot create /path/to/my/dir

```

I checked the help for different snapshots commands and I found `snapshot move-history` and used that to migrate all my snapshots to my new user:

```auto
kopia --config-file=$HOME/.config/kopia/repository.config snapshot move-history ieugen@old-hots-name ieugen@current-host-name

```

restarted Kopia UI and then I removed sources (click on each and click “Remove sources”) for the old snapshots because they where empty.

Now all is good and I have backups again + remote sync to a garage S3 repository 🙂

---

<div class="post-metadata">

**Author:** ![maclm](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/maclm/32/61_2.png) [@maclm](https://kopia.discourse.group/u/maclm)\
**Post date:** [July 12, 2026, 8:53pm UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844/4 "2026-07-12T20:53:10Z")

</div>

Hey!

How do you achieve remote sync to your garage S3 repository?  
Is it that you have a garage node locally?

m

---

<div class="post-metadata">

**Author:** ![ieugen](https://yyz2.discourse-cdn.com/free1/user_avatar/kopia.discourse.group/ieugen/32/467_2.png) [@ieugen](https://kopia.discourse.group/u/ieugen)\
**Post date:** [July 13, 2026, 8:37am UTC](https://kopia.discourse.group/t/solved-kopia-ui-no-longer-takes-snapshots-and-i-cant-run-snapshot-now/8844/5 "2026-07-13T08:37:55Z")

</div>

I have remote garage nodes.

I have a simple script that also has monitoring via [healtchecks.io](http://healtchecks.io) .  
You might want to signal backup start and backup end.

I will have to update my script to do that.

```auto
#!/usr/bin/bash
#

export ACCESS_KEY=REDACTED
export SECRET_ACCESS_KEY=REDACTED
export REGION=garage
export ENDPOINT="s3.REDACTED"
export BUCKET=REDACTED

time kopia repository sync-to s3 --bucket $BUCKET --region=$REGION --endpoint="$ENDPOINT" --access-key="$ACCESS_KEY" --secret-access-key="$SECRET_ACCESS_KEY" >

# Signal we have a backup
curl https://healthchecks.io/ping/REDACTED

```