Login help: identify the access problem

“Password incorrect”, “code expired”, a blank page and an account-review notice describe different problems. Preserve the exact message and approximate time. A screenshot should show the relevant error without exposing a password or recovery code. The browser address helps establish whether the message came from the expected origin.

A forgotten password points to reset. A lost authenticator points to factor recovery. A page that cannot load points first to connection or browser checks. A service restriction needs its own account explanation. Repeating the same login input cannot resolve all of those states.

Write down the error wording and approximate time without recording your password. Check whether the page is the expected official destination and whether the connection completed. A blank page and a rejected password are different observations; describe the one you can actually see.

If the password is forgotten, use the official reset journey. If a second factor is unavailable, read its recovery instructions instead. Avoid switching between several recovery attempts at once, because later messages may refer to a different request from the one you are following.

A message saying the password is incorrect points to the official password or recovery flow, after the destination is established. An expired second-factor code points to that factor’s timing or recovery instructions. An account-review notice points to the service’s review process. Resetting a password in all three cases would not address the same problem.

A blank page supplies less evidence. Note whether it occurs before credentials are entered and whether the browser shows a connection error. Loading problems belong to platform troubleshooting until there is an explicit account-state message.

Recovery material can be more sensitive than an ordinary screenshot. A reset link or backup code can grant access. If support asks to see the error screen, capture the message without including a usable recovery link. If a screen contains private fields, crop or redact those fields.

After access is restored, review the contact details and sessions where controls are available. If you cannot recognise a session, use the service’s established security process. Do not assume a successful sign-in resolves a suspected unauthorised change.

Tell the official support route which recovery step you attempted and what happened. The account reference or contact address can help identify the case, but private authentication material must stay out of the query. Do not approve an unrelated request because someone claims it will fix sign-in.

If the reply simply says to reset the password after you already did, refer to the existing case and explain the unchanged message. Ask whether the issue concerns the password, second factor or account status. Keep one timeline rather than opening several duplicate requests that lose the earlier context.