[BUG] JWT sessions invalidated on every container restart — desktop app requires re-authentication

[tonary]

Title

JWT sessions invalidated on every container restart — desktop app requires re-authentication after every restart/rebuild

Platform

App - Linux

Server Installation Method

Docker

Version

2.2.0

Troubleshooting

• I have examined logs and tried to find the issue
• I have reviewed opened and closed issues
• I have tried restarting the application
• I have read Known Issues (Known Issues (Read Before Posting) #296)

The Problem

Every time the Termix Docker container is restarted or the server is rebuilt, all desktop app (Linux) JWT sessions are invalidated. The desktop app shows the login screen and requires full re-authentication. This makes the desktop app unusable in any setup where container restarts are part of normal operations (updates, rebuilds, maintenance).

How to Reproduce

1. Deploy Termix via Docker, log in via desktop app
2. Restart the Termix container (docker compose restart or rebuild)
3. Open the desktop app — session is gone, re-authentication required

Additional Context

This also affects server rebuilds. After migrating to a new server or rebuilding the Docker environment, the desktop app cannot reconnect without manual re-authentication. For a tool intended to manage production servers, persistent sessions across restarts should be a basic requirement.

[ZacharyZcR]

Fixed in dev-2.3.0 (PR #792): graceful shutdown now flushes in-memory database to disk before exit, preserving sessions across container restarts.