Academy/Troubleshooting

Troubleshooting

Fixes for the most common problems: installer, SmartScreen, sign-in and plans, usage limits, folders, changes and undo, approvals and blocked actions, updates, web jobs and commands — plus SSH/SFTP and web hosting connections (beta) and what to do with the extensions that aren't released yet.

Available Beginner · 10 min · Version: 0.1.2 · Last verified: 2026-11-16

Prerequisites

  • The exact error text, if any (open Show details).
  • The app version.
  1. Read the exact message

    Errors in Paralake.AI explain the cause in plain words. Click Show details to see the technical details, and try Try again. Copy the text exactly — it is what support needs too.

  2. Check the service status

    Open paralake.ai/status to see if sign-in, the AI or billing has an incident.

  3. Check the folder

    Look at 📁 Folder: <name> at the top of the agent view. Many problems come from working in the wrong folder. Click it to switch.

    The folder label arrives with version 0.1.2 – if you don't see it yet, it comes with an automatic update. Until then, choose the folder on Home.

  4. Find your problem below

    Each entry lists likely causes, steps to fix it, and when to contact support. Never disable antivirus, firewall or Windows security as a fix, and never send passwords or keys to anyone — including us.

  5. Contact support

    Contact support at help@paralake.ai, through paralake.ai/support, or — when signed in on the website — under Dashboard → Support → New ticket. Include the app version, what you did, what you expected and the exact error text.

Security

  • Never disable antivirus, firewall, SmartScreen or other Windows security features to make Paralake.AI work.
  • Never send passwords, private keys, API secrets, .env contents or server.cfg secrets to support or into the chat.
  • If someone contacts you claiming to be Paralake support and asks for your password or a remote session you didn't request, don't respond — email help@paralake.ai.

Troubleshooting

Installer won't start

Likely causes: Incomplete or corrupted download. · Antivirus quarantined the file. · The file isn't from paralake.ai.

  1. Download only from paralake.ai/download.
  2. Compare the SHA-256 checksum on the download page with Get-FileHash.
  3. Check your antivirus history; report the detection to us instead of disabling protection.
  4. Restart Windows and try again.

Contact support if: The checksum matches the official page and the installer still won't start, or the official file is flagged. Support

Windows SmartScreen warning ("Windows protected your PC")

Likely causes: The app is not code-signed yet, so the publisher is shown as unknown on the first install.

  1. Check that the file came from paralake.ai and that the SHA-256 matches.
  2. Click More info → Run anyway.
  3. Don't change SmartScreen settings or disable Defender.
  4. Later updates are signed and verified automatically, so this warning only concerns the first install.

Contact support if: The checksum doesn't match, or you're unsure — ask before running it. Support

Sign-in failed

Likely causes: Wrong email or password. · Email not confirmed yet. · No internet connection.

  1. Open Settings → Account & AI and check email and password; reset the password on paralake.ai if needed.
  2. Confirm your email from the message we sent.
  3. Check your internet connection and paralake.ai/status.

Contact support if: Sign-in fails with correct details and a working connection. Support

Plan or trial not showing

Likely causes: Email not confirmed — the trial starts only after confirmation. · A purchase on paralake.ai hasn't reached the app yet.

  1. Confirm your email, then sign in again under Settings → Account & AI.
  2. Check your plan on paralake.ai under Dashboard.

Contact support if: A payment went through on paralake.ai but your plan or extra usage doesn't appear after signing in again. Support

The AI doesn't respond or a step fails

Likely causes: A temporary error or an incident.

  1. Click Try again.
  2. Open Show details and read the error.
  3. Check paralake.ai/status.

Contact support if: It keeps failing for more than an hour with no incident on the status page. Support

Usage limit reached

Likely causes: Your monthly usage (and any extra usage) is spent. · You've reached the short limit that refills after 5 hours. · Too many AI jobs at the same time.

  1. Buy extra usage on paralake.ai (Dashboard → Extra usage) or upgrade.
  2. Wait until the limit refills.
  3. Wait for running jobs to finish.
  4. See the How usage works guide.

Contact support if: Your usage on paralake.ai (Dashboard → Usage) differs from what the app says. Support

The agent works in the wrong folder

Likely causes: Another folder is active. · A new project was put in its own subfolder because the folder already contained other things.

  1. Check "📁 Folder: <name>" at the top of the agent view and click it to switch. (the folder label arrives with version 0.1.2; until then, choose the folder on Home)
  2. Look for the new subfolder inside your folder, or start new projects in an empty folder.

Contact support if: The right folder is shown but files end up somewhere else. Support

A change isn't what I wanted

Likely causes: Apply file changes automatically is on (the default), so changes are written directly.

  1. Click Undo last change to undo the latest step.
  2. Click Start over to restore everything to before the task.
  3. Turn off automatic changes under Settings → Limits if you want to approve each change yourself.

Contact support if: Undo last change or Start over doesn't restore the files. Support

The agent keeps asking for approval

Likely causes: The action needs approval (for example a command or network access). · Deleting files that existed before the task and dangerous actions are always asked.

  1. Choose Always allow for common actions in that project. You can revoke it later.
  2. For deletes and dangerous actions, approve each time or deny.

Contact support if: Always allow is chosen but the same common action is still asked every time. Support

An action is blocked and can't be approved

Likely causes: The action is classed as dangerous and is blocked completely (for example formatting disks).

  1. Ask the agent for a safer alternative.
  2. If you really need it, do it yourself outside Paralake.AI after checking it carefully.

Contact support if: An ordinary action is blocked. Support

An unknown package isn't installed automatically

Likely causes: Without asking, the agent only installs known packages, without install scripts, in projects it created itself. Unknown packages always ask.

  1. Approve the installation if you trust the package, or ask for a known alternative.

Contact support if: A well-known package is always treated as unknown. Support

The agent doesn't change my FiveM resource

Likely causes: The server is running — files in a resource are not changed while the server is running.

  1. Stop the server, let the agent make the change, then start it again.

Contact support if: The server is stopped and the agent still can't change the resource. Support

An update isn't installed

Likely causes: Updates install when the app is closed or when you click Restart and update. · An agent task is running — updates never install in the middle of a task. · Only signed, newer versions are installed.

  1. Let the task finish, then click Restart and update or close the app.
  2. Check Settings → About → Updates (automatic updates and the Stable or Beta channel).

Contact support if: The app never installs an update even though automatic updates are on. Support

Changes from a job on paralake.ai don't appear

Likely causes: Changes from a web job are never written automatically. They are queued and approved locally in the app. · Production requires an extra confirmation.

  1. Open the app on the paired computer or server and approve the queued changes.

Contact support if: You approved the changes locally and they still aren't written. Support

SSH or SFTP connection failed (Save and test)

Likely causes: Wrong host, port or user. · The server only accepts keys, or your public key isn't installed for that user. · The root folder doesn't exist or isn't readable for the user. · SSH/SFTP connections are in beta since 0.1.1, so a bug is possible.

  1. Check host, port (usually 22) and user, and try the same login in your usual SSH or SFTP client.
  2. Check the root folder path and its permissions on the server.
  3. Paste keys or passwords only into the connection form — never into the chat or a ticket.
  4. See the SSH & SFTP connections guide.

Contact support if: The same login works in another SSH/SFTP client but fails in Paralake.AI — include the app version and the error text, never keys. Support

WARNING: the host key has changed

Likely causes: The server was reinstalled or moved. · Someone may be trying to intercept the connection.

  1. Click Cancel and ask your provider or server admin whether the key changed.
  2. Only click Trust key and connect after the new fingerprint is confirmed.
Deploy over SSH/SFTP failed, or the Deploy button is missing

Likely causes: The connection doesn't have Write files permission (the Deploy button only appears with it). · Wrong local folder or folder on the server. · On Production, the host name typed to confirm doesn't match. · Deploy is in beta.

  1. Edit the connection and tick Write files (with backup).
  2. Check the folders and the file list in Preview before deploying.
  3. If a deployment went wrong, click Roll back this deployment, or ask the agent to roll back with the Deploy ID.
  4. Deploy to a Staging connection first.

Contact support if: Rollback fails, or files differ from what Preview showed — include the Deploy ID and the error text. Support

cPanel or Plesk account test failed

Likely causes: Wrong host or port (cPanel usually 2083, Plesk usually 8443). · The API token or key is wrong, expired, revoked or not allowed by your host. · For Plesk, no files via API is expected — Plesk's API has no file management.

  1. Check the host and port in your host's documentation.
  2. Create a new token or key in the panel and paste it into the hosting account form — never into the chat.
  3. For Plesk files, add an SFTP or SSH connection to the site folder.
  4. See the Web hosting, cPanel and Plesk connection guides.

Contact support if: Your host confirms the details and API access, and the test still fails — include the error text, never the token. Support

VS Code extension not connected

Likely causes: The desktop app is not running or you are not signed in. · The folder in VS Code is not a trusted workspace. · The extension was installed from a different VSIX than the one that ships with the app.

  1. Start Paralake.AI and sign in.
  2. Trust the workspace in VS Code.
  3. Reinstall the extension from the VSIX in %LOCALAPPDATA%\Paralake.AI\extensions (Install from VSIX). It is not in the VS Code Marketplace.

Contact support if: It still does not connect after these steps – include the error message. Support

Chrome extension disconnected

Likely causes: The Chrome extension isn't released yet. If you see this, you are either testing a pre-release build or using something that didn't come from Paralake.

  1. Use Preview in the desktop app.
  2. See Install the Chrome extension for status.

Contact support if: You are part of a pre-release test. Support

A command failed

Likely causes: You denied the command, or the approval wasn't answered. · The command is blocked because it is classed as dangerous. · A tool the command needs isn't installed. · The command itself fails (for example failing tests).

  1. Open Show details to read the output.
  2. Install the missing tool yourself, then click Try again.
  3. Ask the agent to explain the error.

Contact support if: A simple command that works in your own terminal fails in Paralake.AI with no useful output. Support

FAQ

Where do I find technical details about an error?

Click Show details on the error.

Will support ask for my password?

Never. Paralake support never asks for passwords, private keys, API secrets or .env contents.

Can I go back to how my folder looked before a task?

Yes. Start over restores everything to how it was before the task. Undo last change undoes only the latest step.