You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
NethLink: version and last access not updated when logging in with a saved session #8284
Log in to NethLink and check the user's NethLink device info in the wizard (Configurations → Preferences → Users → Info): version and "Last access" are populated
Update NethLink to a newer version (or simply close it), keeping the saved session
Open NethLink again: it logs in automatically with the saved token
Check the NethLink device info in the wizard again
Expected behavior
NethLink version, OS and "Last access" reflect the client currently running and its latest start.
Actual behavior
Version and "Last access" still show the values of the last manual login (e.g. old version 1.5.2 after updating to 1.5.3, old timestamp). Presence and SIP user agent are updated correctly, since they come from the SIP registration, not from the heartbeat.
The POST /user/nethlink heartbeat is sent only during an interactive login. When NethLink starts with a saved, still valid token, the auto-login only validates it with /user/me and skips the heartbeat. The same happens on resume from sleep and on socket reconnect.
Suggested fix or workaround
Workaround: log out and log in again from NethLink.
Fix: send the heartbeat also when the auto-login reuses a saved valid token (app start, resume from sleep, socket reconnect), without blocking the login if the heartbeat fails.
Setup: NethVoice >= 1.7.10, a user with a NethLink device, NethLink build from the PR, access to the wizard (Configurations → Preferences → Users → NethLink device → Info).
Test Case 1 - Start with saved session
Log in to NethLink, note version and "Last access" in the wizard Info modal
Close NethLink completely and wait at least one minute
Reopen NethLink: it logs in automatically without asking credentials
Reload the Info modal: "Last access" is updated to the new start time
Test Case 2 - Client update with saved session
With a saved session on an older NethLink (e.g. 1.5.2), install the PR build without logging out
Open NethLink: it logs in automatically
Reload the Info modal: "NethLink version" shows the new version, OS and "Last access" are updated
Test Case 3 - Resume from sleep
With NethLink logged in, put the PC to sleep and resume it
Reload the Info modal: "Last access" is updated to the resume time
NethLink is still logged in and calls work
Test Case 4 - Manual login (regression)
Log out and log in again with credentials (also with 2FA if enabled)
Reload the Info modal: version, OS and "Last access" are updated as before
Test Case 5 - Expired token
With an expired saved token, open NethLink: it re-logs in automatically with the saved password
Reload the Info modal: "Last access" is updated
Test Case 6 - Heartbeat failure does not block login
On a server without the middleware heartbeat endpoint (or with the endpoint failing), open NethLink with a saved session
Auto-login completes normally, no error shown to the user
Activity
tonyco97 commentedon Oct 29, 2026
Test
PR: NethServer/nethlink#250
Setup: NethVoice >= 1.7.10, a user with a NethLink device, NethLink build from the PR, access to the wizard (Configurations → Preferences → Users → NethLink device → Info).
Test Case 1 - Start with saved session
Test Case 2 - Client update with saved session
Test Case 3 - Resume from sleep
Test Case 4 - Manual login (regression)
Test Case 5 - Expired token
Test Case 6 - Heartbeat failure does not block login
tonyco97 commentedon Oct 30, 2026
verified