Issue refreshing the access token while idling (on the logs interface)

[TheMcSebi]

Describe the bug

After about 5 minutes of idling on the web interface (specifically the /logs route) I get logged out. It doesn't log me out if I close the page and reopen it again (way) later than 5 minutes after, so I guess this isn't expected behavior.

To Reproduce
Steps to reproduce the behavior:

1. Login as default admin
2. (visit the Logs interface)
3. Wait for 5 minutes

Step 2 appears to be optional.

Expected behavior
Staying logged in.

Logs

2025-03-03 18:33:39 - INFO - ('192.168.178.132', 50749) - "WebSocket /v3/logs/stream" [accepted]
2025-03-03 18:33:39 - INFO - connection open
(opened the page)
2025-03-03 18:38:08 - INFO - 192.168.178.132:50323 - "OPTIONS /v3/users/refresh-token HTTP/1.1" 200
2025-03-03 18:38:08 - INFO - 192.168.178.132:50323 - "POST /v3/users/refresh-token HTTP/1.1" 200
2025-03-03 18:38:15 - WARNING - 192.168.178.132:50382 - "POST /v3/users/refresh-token HTTP/1.1" 401
2025-03-03 18:38:15 - INFO - 192.168.178.132:50382 - "OPTIONS /v3/users/logout HTTP/1.1" 200
2025-03-03 18:38:15 - INFO - 192.168.178.132:50382 - "POST /v3/users/logout HTTP/1.1" 200
2025-03-03 18:38:15 - INFO - connection closed
2025-03-03 18:38:15 - ERROR - WebSocket error:
(got logged out, log window clears, shows spinning load icon)
2025-03-03 18:43:08 - INFO - 192.168.178.132:50645 - "POST /v3/users/refresh-token HTTP/1.1" 200
(I F5'd)

Desktop (please complete the following information):

• OS: Debian 12
• Browser: Microsoft Edge (yes, really)
• Version: Latest Docker image (v3.4.3 I suppose, couldn't find version info in the logs or in the UI)

Additional context
When I'm on the logs page, there's not much in the client side javascript console, besides "WebSocket connection closed. Reconnecting in 1s..." when the disconnect happens.

On another page it did in fact refresh the page after pretty much exactly 5 minutes (and went to the login screen) with these js messages:

• POST http://192.168.178.165:7272/v3/users/refresh-token 401 (Unauthorized)
• [r2rClient] Refresh call itself returned 401/403 => logging out
• Failed to refresh token: Error: Status 401: Token has been invalidated
• Error fetching documents: Error: Failed to get authenticated client