Why does Mirlo say it needs JavaScript, and how do I enable it?

Updated

Mirlo is a JavaScript-dependent web app, so if JavaScript is disabled or blocked in your browser, the page can't load and shows a message asking you to enable it. This is a browser-side technical requirement, not a problem with your Mirlo account or with the site being down. Enabling JavaScript for mirlo.space (or for all sites) and reloading the page is the fix.

What the message actually means

Mirlo's own page states: "Hi! Mirlo needs JavaScript to run. Please enable it if you want to use it." That message is served as a fallback for browsers that don't execute JavaScript. In other words, the site is built to run in the browser, and without JavaScript there is nothing for it to render.

A few things follow from this:

  • It is not a login or account error. You don't need to sign in, reset anything, or contact support to get past it.
  • It is not necessarily a site outage. If Mirlo were down, you'd typically see a different error (a server error page or a timeout), not a JavaScript prompt.
  • It can appear even if you never intentionally turned JavaScript off. Browser extensions, privacy tools, corporate or school network policies, and some browser settings can block scripts without you realizing it.

How to enable JavaScript in common browsers

The exact menu names vary by browser and version, so treat the steps below as the general path rather than a guaranteed label-by-label match.

Google Chrome (desktop)

  1. Open the three-dot menu and go to Settings.
  2. Go to Privacy and security → Site settings.
  3. Select JavaScript.
  4. Choose Sites can use JavaScript (the default), or add mirlo.space to the allowed list if you prefer to keep JavaScript off globally.
  5. Reload the Mirlo tab.

Mozilla Firefox (desktop)

  1. Type about:config in the address bar and accept the warning, or use Settings → Privacy & Security.
  2. In Settings, scroll to Permissions and make sure Enable JavaScript is checked (Firefox enables it by default).
  3. If you use an extension like NoScript, allow mirlo.space there instead.
  4. Reload the page.

Safari (macOS)

  1. Open Safari → Settings (or Preferences) → Security.
  2. Make sure Enable JavaScript is checked.
  3. Reload the page.

Microsoft Edge (desktop)

  1. Open the three-dot menu and go to Settings.
  2. Go to Cookies and site permissions → JavaScript.
  3. Turn JavaScript on, or allow mirlo.space specifically.
  4. Reload the page.

Mobile browsers

On iOS Safari, JavaScript is on by default and is controlled under Settings → Safari → Advanced. On Android Chrome, use the three-dot menu → Settings → Site settings → JavaScript. If you use a content blocker or a privacy-focused browser, check that app's own settings rather than the system browser.

If enabling JavaScript doesn't fix it

Work through these in order, since each one rules out a different cause:

  1. Hard-reload the page. A cached copy of the fallback message can stick around. Use Ctrl+Shift+R (Windows/Linux) or Cmd+Shift+R (macOS).
  2. Check extensions. Ad blockers, script blockers, and privacy extensions are the most common reason JavaScript is blocked on one site but not others. Disable them for mirlo.space or pause them and reload.
  3. Try a private/incognito window. Extensions are usually disabled there. If Mirlo loads in incognito, an extension is the culprit.
  4. Try a different browser or network. If it fails everywhere on one network but works on another (for example, mobile data vs. office Wi-Fi), a network-level filter is likely blocking scripts.
  5. Confirm JavaScript is actually running. Visit a simple JavaScript-dependent page you trust; if that also fails, the problem is your browser configuration, not Mirlo.

What you should see once it works

After JavaScript is enabled and the page reloads, the fallback message disappears and the Mirlo interface loads normally. At that point you can browse the site as intended — Mirlo describes itself as a place to "buy and sell music directly from musicians," so the loaded app is where that browsing and purchasing happens. If the message persists after all of the above, the remaining possibilities are a browser too old to run the site's scripts or a network policy you can't change yourself.