Kopia Server no connect after upd. to 0.18/0.18.1

Support
1

I have kopia repository server runing behind traefik for many hosts. After update to 0.18.1 the clients didn’t connect to the repository server any more.

After downgrade to 0.17 it is working again:

2024-11-18T06:25:39.596974Z INFO kopia/server starting session for user "backup@client" from 172.30.255.254:53176
172.31.0.1 - - [18/Nov/2024:06:18:09 +0000] "POST /kopia_repository.KopiaRepository/Session HTTP/2.0" 200 84 "-" "-" 96700 "kopia@docker" "https://172.30.0.6:51515" 250ms

Wiht 0.18.1 i got this error:
cli-log:

2024-11-18T06:27:33.490217Z DEBUG auth password error for user 'backup@client': unsupported hash version (0)
access.log
172.31.0.1 - - [18/Nov/2024:06:15:50 +0000] "POST /kopia_repository.KopiaRepository/Session HTTP/2.0" 200 0 "-" "-" 96534 "kopia@docker" "https://172.30.0.6:51515" 44ms

Connection on client:

repository connect server 
 --url="https://kopia.domain.tld:443"
 --override-hostname="client"
 --override-username="backup"
 --enable-actions

what is the problem? must i

2

Same problem with 18.1.

I use kopia-cli to do my backups but kopia-ui to access them. My process is first to mount a sshfs to another box. Then connect to the repository with:

/usr/bin/kopia repository connect from-config --token ey....

which works fine as show with kopia snapsot list and kopia repository status. But kopi-ui simply spins waiting to connect. My next backup is in half an hour so I’ll report further if it fails.

3

I also testet what is returned on both versions via user info at the repository server:

docker exec -ti kopia kopia server user info backup@client
{
“username”: “backup@client”,
“passwordHashVersion”: 1,
“passwordHash”: “ZwfD…pSg==”
}
don’t know why the error report hashVersion as “0”

i also testet setting the user password again with v.0.18.1 via hash, param and readln, no change at all.

4

Sorry about that, could you try the lates build from Releases · kopia/kopia-test-builds · GitHub and see if that fixes the issue.

Unfortunately it turns out we had (at least) 2 backwards-incompatible changes where new version does not work on previously-written data, which were not caught in the code review this time.

If the test build proves to be ok, we’ll cut 0.18.2 release with those changes.

1 Like
5

Same problem here. Using amd64 downgrading to v0.17.0 fixed it:

wget https://github.com/kopia/kopia/releases/download/v0.17.0/kopia_0.17.0_linux_amd64.deb
dpkg -i kopia_0.17.0_linux_amd64.deb

Issue was created for it here Can't connect from some machines after updating to v0.18.1 and also can't set a password · Issue #4257 · kopia/kopia · GitHub and resolved quicker than lightning strikes.

However, we have to be patient for the backwards-incompatible changes jkowalski mentioned to be fixed.

I’d say: don’t upgrade to 0.18-series until the 0.18.3 version is released and downgrade to 0.17 if you have upgraded already and run into issues.

6

Hi,

have testet the docker build “kopia:unstable” as repository server against:

  • kopia client 0.18.1 (win)
  • kopia client 0.17 (win)

both can connect and push their backups to the kopia server.

Thank you very much. I will wait for the next release.

FYI: client 0.18.1 to server 0.17 have worked before.

7

Resolved in latest release (v0.18.2)! Thanks for the quick fix!