Why Orion (orion.lukasbach.com) Shows “You need to enable JavaScript to run this app”
Updated
Orion is a client-side web app built with create-react-app, so its entire interface is rendered by JavaScript. The message “You need to enable JavaScript to run this app” is the static fallback that create-react-app puts in the page's HTML; it is what you see whenever the browser does not execute the app's scripts. To get past it, enable JavaScript for the site (or in general), make sure no extension or browser setting is blocking scripts, and reload. If JavaScript is already on, the app is likely still loading or failed to start, and the steps below cover how to check that.
What the message actually means
The page you receive from the server is essentially an empty shell plus that sentence inside a <noscript> block. The real content only appears after the browser downloads and runs the JavaScript bundle. So the message is not an error from Orion itself — it is the site telling you that the app never got a chance to start. The site's own description confirms the stack: it is a "Web site created using create-react-app."
That distinction matters for troubleshooting: the problem is almost always on the browser side (scripts disabled or blocked), not with your account, network, or the site's server.
Fix it in your browser
1. Enable JavaScript
- Chrome / Edge: Settings → Privacy and security → Site settings → JavaScript → set to Allowed. To allow only this site, add
orion.lukasbach.comunder "Allowed to use JavaScript." - Firefox: Type
about:configin the address bar, accept the warning, and check thatjavascript.enabledistrue. You can also check Settings → Privacy & Security → Permissions. - Safari: Settings → Security → enable Enable JavaScript (on iOS: Settings → Safari → Advanced → JavaScript).
After changing the setting, reload the page with a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on macOS) so the browser fetches the app fresh.
2. Check for script blockers
Extensions are the most common cause when JavaScript is nominally enabled. Temporarily disable, or allowlist the site in:
- Ad and content blockers (uBlock Origin, AdBlock, etc.)
- Privacy extensions and script blockers (NoScript, Privacy Badger, Ghostery)
- Browser modes that restrict scripts, such as strict tracking protection or "reader" modes
If the page loads with extensions off, re-enable them one at a time and allowlist orion.lukasbach.com in whichever one breaks it.
3. Use a current browser
Very old browsers, or embedded webviews inside other apps, may fail to run the modern JavaScript bundle. Open the URL directly in an up-to-date Chrome, Firefox, Edge, or Safari rather than inside an in-app browser.
If JavaScript is already enabled
Then the fallback text is a symptom of the app not finishing its startup, not of scripts being off. Work through these checks:
- Wait and reload. The bundle has to download before anything renders; on a slow connection the blank shell can sit for a while. Reload once and give it time.
- Open the developer console (F12 → Console). Look for red errors such as failed script loads, blocked requests, or a network error on the bundle file. A failed bundle request usually points to a network filter, proxy, or corporate firewall blocking the site's assets.
- Try a private/incognito window. If it works there, a cached file or an extension is the culprit; clear the site's cache and cookies and retry in the normal window.
- Try another network. Some workplace or school networks block scripts or the CDN serving them. A different connection (e.g., mobile hotspot) is a quick way to test this.
- Check whether the site itself is down. If the console shows the HTML loading but the script returning a server error, the problem is on the hosting side and nothing on your machine will fix it; try again later.
Quick reference
| Symptom | Likely cause | Action |
|---|---|---|
| Message appears immediately, every time | JavaScript disabled or blocked | Enable JavaScript; allowlist the site in blockers |
| Message appears, console shows failed script request | Network/proxy/firewall blocking assets | Try another network; check proxy settings |
| Works in incognito but not normal window | Extension or stale cache | Disable extensions one by one; clear site data |
| Blank page with no console errors | App still loading or failed silently | Reload, wait, check console again |
Once scripts run, the fallback disappears and Orion's actual interface loads in its place. If you have followed the steps above and still see only the message, the remaining possibilities are a site-side outage or a network that blocks the app's files — both outside your browser settings.