Troubleshooting
Messages are quoted as Flarebox shows them.
Installing and starting
Section titled “Installing and starting”“Windows protected your PC”
Section titled ““Windows protected your PC””The installers aren’t code-signed yet. Check the file’s SHA-256, then More info → Run anyway.
Nothing happens when I start Flarebox
Section titled “Nothing happens when I start Flarebox”It’s probably already running in the tray. Starting it again brings the existing window forward; check the tray (the ^ in the taskbar).
“Node.js wasn’t found on PATH. Wrangler needs it — install Node, then restart Flarebox.”
Section titled ““Node.js wasn’t found on PATH. Wrangler needs it — install Node, then restart Flarebox.””Install Node.js, make sure node --version works in a new terminal, then quit Flarebox from the tray and start it again. A new PATH only reaches programs started after it changed.
Dev servers
Section titled “Dev servers”“Port 8787 is already in use”
Section titled ““Port 8787 is already in use””Flarebox names the process holding the port. Stop that, or click Use port n to start on the next free one. To make it stick, set the port in the project’s Settings.
“N leftover workerd processes from an earlier crash are still running”
Section titled ““N leftover workerd processes from an earlier crash are still running””Something crashed and left workerd behind, probably still holding ports. Stop them ends only workerd processes whose parent has gone.
“Couldn’t start”
Section titled ““Couldn’t start””| Detail | Fix |
|---|---|
| “This folder no longer has a wrangler config.” | The config was moved or deleted. Rescan, or unpin the project |
| “Fix the config first: …” | The wrangler config doesn’t parse. The message has wrangler’s own error |
| “package.json has no “script” script any more” | The project’s command points at a script that’s gone. Change it in Settings |
| “The old process didn’t exit in time” | Try again. If it repeats, quit Flarebox and check Task Manager for workerd |
Durable Objects and Workflows don’t show
Section titled “Durable Objects and Workflows don’t show”“This wrangler has no Local Explorer API” means the project’s wrangler is too old. Update it in the project (npm i -D wrangler@latest).
Queue delivery fails
Section titled “Queue delivery fails”“Delivering queue batches needs wrangler installed in the project (npm i -D wrangler).” It can’t run through npx.
An R2 key looks wrong after an upload
Section titled “An R2 key looks wrong after an upload”wrangler’s local R2 commands treat the key as a URL path, so spaces, #, ? and // change it. Flarebox refuses keys that wouldn’t be stored as typed. See Local data.
Tokens
Section titled “Tokens”“Cloudflare didn’t accept this token”
Section titled ““Cloudflare didn’t accept this token””It may have expired, been rolled or deleted, or be limited to other IP addresses. Check it under My Profile → API Tokens in the dashboard, or create a new one.
“This token isn’t allowed to do that. It needs the permission “…”.”
Section titled ““This token isn’t allowed to do that. It needs the permission “…”.””Add the named permission to the token in the dashboard (editing a token keeps its value), then reload the view. See Permissions by view.
“Cloudflare says this token is status: it wasn’t saved.”
Section titled ““Cloudflare says this token is status: it wasn’t saved.””The token is disabled or expired in Cloudflare. Flarebox only stores tokens that verify.
“Couldn’t open the credential store”
Section titled ““Couldn’t open the credential store””Windows Credential Manager couldn’t be opened, which usually means a locked-down profile. Flarebox won’t store tokens anywhere else.
“Reads are using your write token”
Section titled ““Reads are using your write token””You’ve only stored a write token. Add a read-only token so the write token is only loaded for changes.
My Global API Key is refused
Section titled “My Global API Key is refused”On purpose. Create a scoped API token instead: Tokens and permissions.
Cloudflare API
Section titled “Cloudflare API”“Cloudflare’s rate limit was reached (shared with the dashboard and your other tokens)”
Section titled ““Cloudflare’s rate limit was reached (shared with the dashboard and your other tokens)””Cloudflare allows 1,200 requests per 5 minutes per user, counted across the dashboard and every token. Wait the minutes given. Flarebox paces itself to 1,000, so this usually means another tool used the rest.
“No answer from Cloudflare in time … The change may or may not have applied”
Section titled ““No answer from Cloudflare in time … The change may or may not have applied””The write timed out. Re-read the view to see whether it applied before trying again. Flarebox never retries a write that might have gone through.
“… changed since you reviewed it (perhaps in the dashboard). Review it again.”
Section titled ““… changed since you reviewed it (perhaps in the dashboard). Review it again.””Someone changed the same thing between your review and your confirm. Nothing was written. Review the new state and apply again if you still want the change.
An “Offline” marker
Section titled “An “Offline” marker”Cloudflare couldn’t be reached, so Flarebox shows the last state it saw. Changes are unavailable until it’s back.
Tunnels
Section titled “Tunnels”“cloudflared isn’t installed”
Section titled ““cloudflared isn’t installed””winget install --id Cloudflare.cloudflaredThen restart Flarebox. If it’s installed somewhere unusual, set FLAREBOX_CLOUDFLARED to its path.
Origin checks
Section titled “Origin checks”“Not reachable from this machine”
Section titled ““Not reachable from this machine””Normal for an origin that only accepts connections from Cloudflare’s IPs, as a locked-down origin should. Check it from a server that can reach it, with the pqdoctor CLI.
“No reliable reply”
Section titled ““No reliable reply””The origin answered with nothing but timeouts or resets: down, firewalled or rate-limiting. Re-check in a minute. See no-reply.
Still stuck?
Section titled “Still stuck?”Email hi@kalyangopalam.com with the message, what you clicked, and your Flarebox version (Settings).