Compare account-specific evidence before changing the network
If one local user cannot sign in while another can reach the same server, preserve that distinction. A connection-style message does not prove every part of the server is offline. Repeatedly retrying a password can also obscure whether the account has reached the configured failed-attempt limit.
Read the documented lockout behaviour
Jellyfin’s management guide says failed-login limits can disable a user and shows a Connection Failure message for that condition. It directs the administrator to the dashboard activity information and disabled-user setting for a manual unlock. This is an account-state check, not a reason to disable lockout protections or open unrelated firewall ports. The exact configured limit belongs to that server and user.
Use the responsible administrator’s route
For example, a household member who recently mistyped a password on a television should stop repeated attempts and ask the server administrator to inspect the relevant account state. The administrator can verify the person and review the disabled flag through the supported management interface. After an authorised correction, try the intended user once on the correct server. If the failure remains, retain that result and investigate the actual message rather than assuming lockout explains every network error. Keep passwords and recovery information out of public reports, and do not send an administrator’s credentials merely to avoid the user-specific check.
Questions, answered
Does this message always prove the whole server is down?
No. Jellyfin’s documentation also shows it in a user-lockout context.