The CCS Runner is not loading — what should I do?

CCS Runner won’t load — Troubleshooting Checklist

Use this step-by-step guide to fix common loading issues with CCS Runner. Work from top to bottom. If you’re still stuck, collect the details at the end and send them with your ticket.

Quick checks (1–2 minutes)

Use a supported browser: Chrome, Firefox, or Edge (latest stable version).
Try a Private/Incognito window: If it loads here, the issue is cache or an extension.
Try another browser and/or device: Helps isolate if the issue is browser-specific or machine-specific.

1) Browser

Update your browser to the latest version.
Disable extensions temporarily (especially ad blockers, privacy tools, password managers, VPN/proxy helpers):
- Chrome/Edge: Menu → Extensions → toggle Off. Then reload CCS Runner.
- Firefox: Menu → Add-ons and themes → Extensions → toggle Off.
Disable VPN/Proxy (if possible) and retry.
Optional (graphics issue): Turn off hardware acceleration, restart the browser, and retry.
- Chrome/Edge: Settings → System → toggle off Use hardware acceleration when available.
- Firefox: Settings → General → Performance → uncheck Use recommended performance settings, then uncheck Use hardware acceleration.

2) Clear cache / site data

Recommended approach: clear data for the CCS Runner site only (safer than clearing everything).

Chrome/Edge: Open the CCS Runner page → click the padlock in the address bar → Site settings → Clear data (or Reset permissions), then reload.
Firefox: Open page → padlock → Clear cookies and site data… → reload.

If problems persist, do a broader clear:

Chrome/Edge: Settings → Privacy & security → Clear browsing data → Cached images and files + Cookies and other site data → Clear. Restart browser and log in again.
Firefox: Settings → Privacy & Security → Cookies and Site Data → Clear Data… → select both → Clear. Restart and log in again.

3) Network

Minimum: Stable connection of 5 Mbps+.
Try a different network: switch from corporate Wi-Fi to mobile hotspot (or vice-versa) to rule out local firewalls.
Turn off VPN or corporate proxy if allowed, then test again.
Flush DNS (optional):
- Windows: Open Command Prompt as Admin → run ipconfig /flushdns.
- macOS: Open Terminal → run sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder.

Sign out of CCS Runner (and SSO, if used), then sign back in.
Allow third-party cookies if your SSO/IdP or assets load from another domain (temporarily, for testing).
Check system date/time: Incorrect clock can break secure connections — set to automatic time.

5) Advanced browser reset (optional)

New browser profile: Create a fresh Chrome/Edge profile and try CCS Runner there.
Service worker / storage reset (if the app is a PWA):
1. Open the CCS Runner page.
2. Open DevTools (F12 or Ctrl/Cmd+Shift+I).
3. Go to Application (Chrome/Edge) or Storage (Firefox).
4. Under Storage, clear Local Storage, Session Storage, and Cache Storage for the site. If visible, Unregister the Service Worker.
5. Reload the page.

Still stuck?

Please submit a ticket and include the details below so we can help faster.

What to include

OS & version: e.g., Windows 11 23H2, macOS 14.x.
Browser & version: e.g., Chrome 128.x, Edge 128.x, Firefox 129.x.
Exact time (with timezone) of the failure and your network location (office/home/VPN).
Steps to reproduce (what you clicked, which URL, before it failed).
Screenshots of the issue (include any error messages on screen).
Console errors & HAR file (instructions below).

How to capture Console & HAR

Open CCS Runner.
Press F12 (or Ctrl/Cmd+Shift+I) to open DevTools.
Click Network tab, enable Preserve log and Disable cache.
Reload the page and reproduce the problem.
Right-click inside the Network request list → Save all as HAR with content.
Click the Console tab → right-click → Save as… (or copy/paste visible errors).
Attach the HAR and Console files to your ticket.

FAQ

Blank page or endless spinner? Try a Private window, then clear site data and disable extensions. Check Console for red errors.
Works on hotspot but not office Wi-Fi? Likely a firewall/SSL inspection or DNS issue — include your office network details in the ticket.
“Not authorized” after login? Sign out of both CCS Runner and your SSO, then sign back in. Ensure third-party cookies aren’t blocked.