Troubleshooting
Share
Open the browser’s developer console first. Find the message below.
The Account Button Is Missing
Section titled “The Account Button Is Missing”| Console Shows | Meaning |
|---|---|
Access to script at 'https://accounts.aidenkt.com/kit/…' … blocked by CORS policy |
The site’s origin is not registered on an app (or not on the allowed list) |
GET https://accounts.aidenkt.com/kit/kit.<hash>.js net::ERR_ABORTED 404 |
The kit was updated and the old file is gone. Copy fresh tags from the app’s page in the portal |
Failed to find a valid digest in the 'integrity' attribute |
The tags do not match the deployed kit. Copy fresh tags; never edit a hash by hand or drop integrity |
| A Content Security Policy message | The named directive is missing https://accounts.aidenkt.com |
| Nothing | The script tag is missing, lacks defer, or CSS hides [data-kt-account]. window.ktAccounts is undefined when the script did not run |
The Element Looks Empty
Section titled “The Element Looks Empty”Normal. The button is drawn inside a shadow root. data-kt-ready on the element says whether it was drawn.
The Button Is a White Pill Although line Was Asked For
Section titled “The Button Is a White Pill Although line Was Asked For”The contrast check: the element has data-variant="float" data-variant-wanted="line". The bar’s text colour does not stand out from its background-color. A background image or gradient is not seen by the check, so give such a bar a background-color as well.
GET https://accounts.aidenkt.com/api/whoami 401
Section titled “GET https://accounts.aidenkt.com/api/whoami 401”Normal when nobody is signed in. If someone just signed in, the browser is blocking cookies between subdomains, or the sign-in happened in another browser profile.
CSP Violations
Section titled “CSP Violations”The directive named at the end of the message is the one missing the accounts origin: script-src (the kit), style-src (its stylesheet), font-src (fonts), img-src (profile pictures), connect-src (/api/whoami; always signed out).
OpenID Connect
Section titled “OpenID Connect”| Symptom | Meaning |
|---|---|
| KT Accounts shows an error page instead of returning to the app | The client_id or redirect_uri is wrong. Redirect URIs are compared exactly |
invalid_grant from the token endpoint |
The code is older than 60 seconds, was already used, or the redirect_uri or code_verifier does not match |
invalid_client (401) |
Wrong client secret, or a public client sent a secret it does not have |
access_denied on the callback |
The person chose Cancel |
| Tokens stop working | The person removed the app in Account Settings, the app was suspended, or the person’s permissions or sign-in methods changed |
The Page Shows Signed In, but the Server Helper Returns null
Section titled “The Page Shows Signed In, but the Server Helper Returns null”Expected on a real site: a site’s own server never receives the KT session cookie. See Check Sign-In on a Server.