Rapid Flow logo
Rapid Flow logo
All articles

Let's Go never opens a browser, or activation says Request timed outUpdated 5 days ago

This has not been a fault in the plugin. Please follow the steps for your computer, then try activation once more.

Windows

Use these checks when Let's Go does not open a browser, or when activation stops at Request timed out. Work from the top. Stop when a browser opens and you can sign in.

1. See whether Windows can open a web page at all

  1. Press the Windows key and R together. Type https://example.com and press Enter. A browser should open.
  2. Open Command Prompt, type start https://example.com, and press Enter.
  3. Click a link in another program, such as your email.

If none of those open a browser, Windows is not handing pages to a browser. Continue with the next section. If they do open a browser, skip to section 3.

Choosing a default browser is not always enough. On Windows 10 or 11, open Settings, then Apps, then Default apps. Select your browser and set it for HTTP, HTTPS, .htm, and .html.

The plugin opens the page through those web-link types. If HTTP or HTTPS is not assigned, Let's Go can do nothing even when a saved HTML file still opens.

At the bottom of Default apps, choose Reset all default apps, then set your browser again. If a default-app fixer or a registry cleaner has been used, that reset is the fix. You do not need to edit the registry.

3. A window may be hidden behind the DAW

Windows sometimes asks "How do you want to open this?" behind the DAW, especially in full screen. After you click Let's Go, press Alt+Tab or minimize the DAW and look for that question.

Then close every Brave and Edge process in Task Manager, including the ones running in the background, and try Let's Go again. A browser that is already stuck open can swallow the request.

4. Do not run the DAW as administrator

This is a common cause. Right-click the DAW shortcut or its .exe, open Properties, then Compatibility. If "Run this program as an administrator" is ticked, turn it off. Start the DAW normally and try again.

5. How the DAW hosts the plugin

  • A sandbox or a bridge can block the browser. That includes Bitwig's sandbox, Reaper's "run as separate process" or bridging, a Studio One or Cubase 32-bit bridge, and jBridge. Load the plugin without the sandbox or the bridge and try again.
  • If you have another DAW, try Let's Go there.
  • Use the latest installer from your Moonbase library. On Windows, use the VST3.

6. Security software

Antivirus tools such as Bitdefender, Kaspersky, Norton, or Malwarebytes can block an audio program from opening a browser. Check the log or quarantine. You can turn that protection off for one test, then turn it back on.

In Windows Security, open Protection history. Also check Controlled folder access and Exploit protection for the DAW.

On a work computer, a company policy can block other programs from opening a browser.

7. Try another Windows user

Create a new local Windows account and test the plugin there. If Let's Go works on that account, the problem is this Windows user, not the plugin.

8. If you want to see what Windows is doing

This step is optional. Process Monitor, from Microsoft Sysinternals, can watch the DAW while you click Let's Go. It shows whether the DAW tries to open a browser, and what error comes back. Event Viewer, under Windows Logs and then Application, shows errors from that same moment. The plugin may also write a log under %APPDATA% or Documents, in a Rapid Flow folder.

You can also open the license page yourself. Sign in at rapidflow.moonbase.sh with the email you used at checkout.

If it still fails, reply and tell us whether the Windows+R check opened a browser.

Mac: the browser says the license worked, but the plugin asks again

The license file is damaged. The only known cause is moving from a cracked copy to a licensed copy. The file license.mb is exactly 100 bytes, which is not a normal license.

  1. Quit the DAW.
  2. In Finder, open your home folder, then Library, then Rapid Flow. If you do not see Library, click Go in the menu bar while holding the Option key.
  3. Open the folder for the plugin that is failing.
  4. Delete only the file license.mb.
  5. Open the DAW and activate the plugin again.

Do not delete the Rapid Flow folder itself. It also holds your presets and, for Zensphere, the factory samples.

Mac: the license does not stick, or settings and presets are not saved

The folders that store the license, the settings, and the presets are owned by another account, or they cannot be written. This only changes the owner and the permissions. It does not delete anything, and it is safe to run even if nothing is wrong.

  1. Quit the DAW.
  2. Open Terminal from Applications, then Utilities.
  3. Paste the line below and press Return. Type your Mac password when asked. Nothing appears while you type it.
1for d in ~/Library/"Rapid Flow" ~/Library/"Application Support/Rapid Flow"; do [ -e "$d" ] || continue; echo "Fixing $d"; sudo chown -R "$USER" "$d" && sudo chflags -R nouchg "$d" && sudo chmod -R -N "$d" && sudo chmod -R u+rwX "$d"; done

Then paste this line. If it prints nothing, the folders are fixed:

1find ~/Library/"Rapid Flow" ~/Library/"Application Support/Rapid Flow" \( ! -user "$USER" -o ! -perm -u+w -o -flags +uchg \) -print 2>/dev/null

If it prints file paths, send that text to us. Then open the DAW and activate again.

Do not delete the Rapid Flow folders. They hold your presets and, for Zensphere, the factory samples.

Was this article helpful?
Powered by