How to diagnose the most common Media Console failures yourself, starting with the checks the Console already runs for you.
01Start at the Security page
The Console's Security page is a diagnostic surface, not a marketing badge. It runs four real checks and reports what it actually found.
- Connection. Whether the page is running in a secure browsing context. A failure here means the session is not on HTTPS, and nothing else on the page should be trusted until it is fixed.
- Email verified. If this fails, the alert next to it carries a working resend action rather than sending you away to look for one.
- Multi-factor auth. The count of second factors genuinely enrolled on the account, read live from the auth provider.
- Data plane. A real round-trip against the database with its true latency in milliseconds. While it is in flight it says so; if it fails, it shows the actual error rather than an invented number.
Sections of that page with no real backing source are labelled as such. A blank value means we have no honest number to show, not that the number is zero.
02Sign-in problems
"Too many attempts, wait and try again." Repeated failed password attempts on the same address trip a temporary lock on the sign-in form. Waiting it out is the fix; there is nothing to clear.
A vague "check your credentials" message. The sign-in screen deliberately does not distinguish "no such account" from "wrong password". That is an anti-enumeration measure, not a bug, and it means the message will not tell you which half was wrong.
Your password is right and it still fails. If the account has a second factor enrolled, a correct password is supposed to be followed by a code prompt. If you get an outright failure instead of a code box, you are almost certainly on a client that predates second-factor support.
Second-factor code rejected. Check the clock on the phone running your authenticator first — some drift is tolerated, a badly wrong clock is not. If the sign-in has been sitting for a while, the pending session can expire; start the sign-in again rather than retyping codes.
Lost the authenticator. Use a recovery code from the set you saved at enrollment. A password reset will not help — it does not clear a second factor. If the codes are gone too, identity has to be verified out of band before anyone can clear the factor, so expect that to take a human and some proof.
03Work that will not save
The canvas editor saves continuously on a short flush loop rather than only when you press save, and it warns before you close a tab while edits are still inside that window or a save has failed. Take that warning seriously — it is the one gap where closing a tab loses work. If you see it, cancel, wait a moment, and confirm the save landed before closing.
If saves are failing repeatedly, run the Security page's data-plane check. A failed round-trip there tells you the problem is the connection to the data layer, not the editor.
04Desktop apps versus the browser
The desktop companion builds package a snapshot of the web application. If a feature works in the browser and not in the desktop app, the most likely explanation is that the packaged build predates it. Verify in a browser before reporting a defect, and say which one you were using when you do.