Skip to content

Troubleshooting

The messages you may see in REM Vibe Coder, what each means and what to do.

You see

What it means

What to do

The sign-in took too long or was started in another tab. Please try again.

The sign-in started more than 10 minutes ago, or in another browser (for example you confirmed your e-mail on your phone)

Click Continue With REM Auth and sign in again

You are out of Vibe Coder credits…

Your balance is at zero

Top up or change plan on Plan & credits; in an organisation, ask an admin

Only your organisation's admins change the plan or buy credits.

Your organisation pays, and you are not one of its admins

Ask an admin of your organisation

Plans are not on sale here yet.

Billing is not switched on for this Vibe Coder yet

Keep building on your current allowance; write to support for a plan

Found an issue, fixing it… (round 2)

A check failed and Vibe Coder is fixing it

Nothing; wait. It is not an error

A check in red at the end

The check still failed after three rounds

Read the card (expected, actual, screenshot), then write what to do: "try again", or describe the right behaviour

Restoring your previous session…

The project's sandbox was asleep after 30 idle minutes

Wait about a minute; your code is intact

Your app is waking up. It shows here in a moment.

The preview is starting

Wait; use Restart preview if it stays for minutes

Needs you on a project

A question or permission card waits for your answer

Open the chat and answer the card

Reconnecting… in the chat header

The live connection to the build dropped (network, laptop asleep)

Nothing; it reconnects and replays every step you missed. Reload the page if it stays

Deploy failed

REM CloudHub could not build or start the app

Read the reason on the card; Redeploy, or ask "fix the deploy"

QCH did not answer; try again in a moment (Settings > Memory, MCP servers, Skills)

REM CloudHub did not answer in time

Try again later; builds are not affected. Send the Reference code to support if it persists

Redeploy did not start.

A deploy is already moving, or REM CloudHub refused it

Wait for the current deploy; read the message

A page says not found for a chat someone sent you

Chats and projects are private to their owner

Ask them to share the deployed app instead

Still stuck?

Use Send feedback in the account menu (it includes the page you are on), or write to support@remplatforms.com with the chat link and the Reference code from the message, if there is one. Never send your password.

Last updated 18 Nov 2026

Troubleshooting | REM Vibe Coder · REM Platforms Blog