Skip to content

Troubleshooting — Browser & cache

Common when the Console "looks broken" but you can sign in. This page covers cache misbehaviour, extension interference, advanced DevTools triage, and the rare-but-real situations where you need to factory-reset the SPA in your browser.

Decision tree

graph TD
    A[Console misbehaving] --> B{Symptom}
    B -->|"Blank or partially blank page"| C[Hard-reload]
    B -->|"Works in incognito, not normally"| D[Extension]
    B -->|"CORS / 403 in DevTools"| E[Token / proxy]
    B -->|"CSP errors in console"| F[CSP misconfig or injection]
    B -->|"Old data showing"| G[Cache / CDN]
    B -->|"Forms not submitting"| H[Cookie / SameSite]

    C --> C1[Ctrl+Shift+R]
    D --> D1[Disable one at a time]
    E --> E1[Inspect Network tab + Authorization header]
    F --> F1[Inspect Console tab + 'Refused to load']
    G --> G1[Force refresh + check edge cache]
    H --> H1[Try incognito]

Hard reload

The single most effective fix for "the page looks wrong". Hard reload skips the disk cache and re-fetches the SPA bundle from origin:

OS / browser Shortcut
Windows / Linux (Chrome / Edge / Firefox / Brave / Vivaldi) Ctrl + Shift + R
macOS (Chrome / Edge / Brave / Vivaldi) Cmd + Shift + R
macOS (Safari) Cmd + Option + R
Firefox (alt) Ctrl + F5

If hard reload doesn't fix it, escalate to clear local state below.

"It works in incognito but not in my normal browser"

Almost always a browser extension. Most common culprits:

Extension class Why it breaks Cloud Digit
Ad blockers (uBlock Origin, AdBlock Plus) Aggressive lists block legitimate analytics calls the SPA expects
Privacy extensions (Privacy Badger, DuckDuckGo Privacy Essentials) Block tracking pixels that the auth flow uses for fraud detection
Script blockers (NoScript) Block first-party scripts
Corporate DLP / CASB Inject middleware that breaks WebSocket connections
Password managers (rare) Aggressive form autofill mis-fills hidden fields

To narrow down:

  1. Open the failing tab in incognito — if it works, the issue is an extension or session-data
  2. Open chrome://extensions (or equivalent) and disable extensions one by one
  3. After each disable, reload the Cloud Digit tab
  4. The extension whose absence makes Cloud Digit work is the culprit
  5. In that extension's settings, add an exception for your Cloud Digit domain — usually under "Trusted Sites" or "Allowlist"

CORS or 403 errors in DevTools

Open DevTools (F12) → Network tab → reload → look for red rows.

Pattern Likely cause Fix
403 Forbidden on every API call Session expired silently Sign out, sign back in
403 Forbidden on some API calls only Insufficient role Verify role in Access; see Roles & permissions
CORS preflight failed Browser blocked the OPTIONS request Usually a corporate proxy rewriting headers — escalate to IT
401 Unauthorized on first call only, then OK Token refresh race; benign Ignore
404 on a known-valid URL Wrong region in the URL Check the Cd-Region header — should match the resource's region
429 Too Many Requests API rate limit Slow down; respect the Retry-After header

CSP errors

If you see Refused to load the script… or Refused to execute inline script… in the DevTools Console:

Pattern Likely cause Fix
script-src violation for a Cloud Digit URL Browser plugin injecting a stricter CSP override Disable the plugin
script-src violation for an unknown URL A different extension / malware injecting code into the page Inspect the URL; reset extensions; consider an antivirus pass
connect-src violation for wss:// WebSocket blocked by corporate proxy Allow wss://api.<your-domain> outbound on 443
frame-ancestors violation Trying to iframe Cloud Digit (we deny this) Don't iframe

"Old data showing"

The console caches certain data client-side for snappy interactions. Stale-data symptoms and fixes:

Symptom Cause Fix
Just-created resource not in list Cache hasn't refreshed Top bar → Refresh button (or F5)
Cost figures look 24h stale Cost data is recomputed daily/hourly See Cost Explorer → data freshness
Quota change not reflected Quota cached for 5 min Wait 5 min, or hard-reload
Newly-invited member can't sign in Invite hasn't reached their mailbox yet Check email; resend from Members → ⋯
Status page shows incident but Console is fine CDN edge serving stale; or your region not affected See Status directly

If hard reload doesn't refresh, clear local state (next section).

Clearing local state

When the Console gets into a stuck state that hard-reload doesn't fix:

  1. Open DevTools (F12) → Application tab
  2. Local Storage → your Console domain → Clear All
  3. Session Storage → your Console domain → Clear All
  4. Cookies → your Console domain → delete all entries
  5. IndexedDB → your Console domain → delete the databases
  6. Close DevTools
  7. Hard-reload the page
  8. Sign in again

This is the equivalent of factory-resetting the SPA in your browser. The platform-side state is untouched; only client-side caches are wiped.

If the sign-in form submits but you bounce back to the sign-in page:

  1. DevTools → ApplicationCookies — look for cookies on your Cloud Digit domain
  2. Confirm there's a session cookie (typically KC_SESSION_* or similar)
  3. Check the cookie's SameSite attribute:
  4. Lax (good)
  5. Strict (can break cross-site redirect from IdP — switch to Lax)
  6. None; Secure (good, but requires HTTPS)
  7. If cookies aren't being written at all, your browser's cookie policy is too restrictive — allow third-party cookies for your Cloud Digit + IdP domains

Browser-specific quirks

Browser Quirk
Safari (iOS) Reader mode can hide some controls — open the actual page
Safari (macOS) "Prevent cross-site tracking" can break SSO — disable for Cloud Digit domain
Brave Aggressive shields — disable for Cloud Digit domain
Arc Boost overrides can inject CSS — check Boost is off for Cloud Digit
Firefox Container tabs isolate sessions — ensure you're in the right container
Chromium with strict-extensions corporate policy Corp policy may disable necessary features — escalate to IT

Advanced: DevTools triage

When opening a support ticket about a Console issue, attach:

  1. Console tab screenshot — capture red error rows
  2. Network tab screenshot for the failing request — Headers (request + response) + Response body
  3. Trace ID from the response — Cloud Digit includes X-Cd-Trace-Id in every API response; copy it
  4. Browser versionchrome://version or equivalent
  5. Reproduction URL — the exact URL that fails
  6. Whether incognito reproduces — yes/no

A ticket with these elements gets a first response 5× faster than one without.

When to open a ticket

Open a ticket when you've worked through this page and:

  • The same error repeats in incognito (rules out extension)
  • DevTools shows an unexpected error code
  • Hard reload + clear-local-state doesn't help
  • Multiple users in your org see the same symptom

Include the artefacts listed in Advanced: DevTools triage above.