Duplicati-server-util Failed to refresh token

[kennymc-c]

I’m using the Linuxserver Duplicati Docker image on Unraid and until recently the login token via the duplicati-server-util cli was saved without any issues even after restarting the container, but for some time now, that doesn’t seem to be working anymore.

At first, the login command within the container works, and a token is supposedly saved:

Logging in to the server
Connecting to ``http://127.0.0.1:8200/``...
Logged in, persistent token saved

But when I start a backup immediately afterward using run, the refresh token cannot be used:

Connecting to ``http://127.0.0.1:8200/``...
Failed to use refresh token: Server error (401): Failed to refresh token
Failed to obtain a signin token: Server error (401): Failed to sign in

What’s going wrong here? The /config directory is mounted on the host. What’s strange is that immediately after the login command, no token can be found without the container having been stopped or restarted.

[drizuid]

provide your docker run and your container logs. Please provide text as text not pictures of text. if you dont know how to get the docker run, dont randomly paste something else, google how to get the docker run

i should also note that duplicati changed how refresh tokens work in aug 2025 (and a couple times just before that). you dont define what "some time" is, but maybe this will reveal something

[kennymc-c]

It could be the change in August you mentioned. I just wondered why the login commands says a token was created when the run commands can't find this token.

As I use Unraid this is the command to create the container:

/usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='duplicati' --net='bridge' --pids-limit 2048 -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="smartserver" -e HOST_CONTAINERNAME="duplicati" -e 'PUID'='99' -e 'PGID'='100' -e 'SETTINGS_ENCRYPTION_KEY'='xxx' -e 'DUPLICATI__WEBSERVICE_PASSWORD'='xxx' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:8200]/' -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/duplicati-icon.png' -p '8200:8200/tcp' -v '/mnt/user/':'/source':'rw' -v '/mnt/user/appdata/duplicati/cert/':'/cert':'rw' -v '/mnt/user/appdata/duplicati/config/':'/config':'rw' -v '/tmp/duplicati/':'/tmp/':'rw' --name=duplicati 'linuxserver/duplicati'

Log:

[migrations] started
[migration] no migrations found
usermod: no changes

Brought to you by linuxserver.io
To support LSIO projects visit:
https://www.linuxserver.io/donate/

GID/UID
User UID: 99
User GID: 100

Linuxserver.io version: v2.3.0.1 stable 2026-04-24-1s291
Build-date: 2026-05-02T05:58:35+00:00

[custom-init] No custom files found, skipping...
[ls.io-init] done.
Server has started and is listening on *, port 8200

[drizuid]

i dont personally use duplicati, but the changes last year were basicaly around a new client not doing refresh tokens at all, then in august was an overhaul to make them work properly.. it sounded like a big issue was they would logout after 15 minutes and since some backups took longer than 15min, the whole app would crash since once the backup finished, the user was no longer authed. it SEEMED like this was fixed and based on your lsio version, shown in the log, you should be on that latest version. let us bounce this around internally, but please do drop in our discord as well, it's much more real time (and in front of us)

[kennymc-c]

I noticed that a settings.json is created in /config right after I use the login command which contains the refresh tokend. So I assume it's not a mapping problem.

Another thing: I just got logged out of the web interface in the middle of a running backup and my password didn't work anymore when I tried to login again. Nothing in the log about this. I restarted the container and it worked again.