Skip to content

Troubleshooting

Find your problem below. If it isn’t here, send us your logs.

“yoghurtbot.io could not start”. Another copy is probably already running. Check the system tray, close it, and try again.

The components window keeps failing. Click Try again. If it still fails, check that your antivirus or firewall isn’t blocking the download.

“The system detected an overrun of a stack-based buffer”, or the bot closes as soon as it opens. Windows Security has probably removed one of the bot’s files. Tell it to leave the bot alone, as below.

The bot closes by itself with no message. Windows keeps a note of why. See Check Windows Event Viewer.

Stop Windows Security removing the bot’s files

Section titled “Stop Windows Security removing the bot’s files”

You add two folders to its exclusions: the bot’s data folder, and the folder yoghurtbot.exe is in.

  1. Open the Start menu, type Windows Security and open it.

  2. Click Virus & threat protection. Under Virus & threat protection settings, click Manage settings.

  3. Scroll down to Exclusions and click Add or remove exclusions. Click Yes when Windows asks.

  4. Click Add an exclusion, then Folder. Paste this into the address bar at the top, press Enter, then click Select Folder:

    %APPDATA%\yoghurtbot.io
  5. Click Add an exclusion and Folder again. Pick the folder yoghurtbot.exe is in, then click Select Folder.

  6. Open the bot again. It puts back any of its files that were removed when it starts.

If yoghurtbot.exe itself has gone, download it again from the dashboard into the folder you excluded.

Using a different antivirus? Add the same two folders to its exclusions. The setting is usually called exclusions, exceptions or allowed apps.

The browser didn’t open. Click Copy the approval link and paste it into your browser.

It stops on startup with a licence message. Your licence has expired. Renew it on the dashboard within 7 days, or it’s removed for good. See Your licence.

“This licence is already active on another PC”. Your licence works on one PC at a time. See Devices to move it.

The connection pill on Home says Paused. New tasks won’t start until the bot reconnects. Running ones carry on. Check your internet connection. See The connection light.

Start does nothing on some tasks. They’re probably disabled. Look for the Disabled badge, then right-click and choose Enable tasks.

A monitor didn’t start its tasks. Check they’re in the same task group, for the same store and product, and that you didn’t stop them by hand. See Which tasks a monitor starts.

You see Try this
Red statuses across many tasks at once Test the proxy group and delete what fails. Then mass edit the tasks onto a fresh group.
A task waiting with no progress A captcha may be waiting for you. Open Captcha solver on the Tasks page.
Captcha -> waiting for a free solver Every captcha service is at its Max concurrent solves. Raise the limit or add another service in Settings › Captcha.
“No captcha service has … ticked” Tick that kind of captcha on one of your services in Settings › Captcha.
“hCaptcha AI is off and no captcha service has hCaptcha ticked” Turn hCaptcha AI back on, or tick hCaptcha on a 2Captcha service.
A window asking you to Enter the code The store emailed a sign-in code. Type it in, or connect the inbox so tasks enter codes themselves.
Amazon: “no delivery address on the account for Turbo” Add a delivery address to the Amazon account.
Shopify: “Can’t preload: not found” The keyword matched nothing. Check the query, or switch to Fast or Safe so the task keeps searching.
Shopify: “needs a Checkout One store” That store uses the older checkout. Use Fast or Safe, set Payment to Card, and put one product on the task.

Logs show us exactly what a task did, which is the quickest way for us to find a problem.

  1. Go to Settings › General and click Send logs.

  2. Describe what happened: the store, the time, and what the status said.

  3. Click Send.

This uploads your latest log files, any task traffic you recorded, and basic PC details: Windows version, CPU, memory and graphics.

The bot sends us a report by itself when it crashes, and when a task stops on a problem or hits an error. You don’t need to do anything. If you’re offline at the time, the report goes the next time you open the bot.

A report holds:

  • what went wrong, and where in the bot it happened
  • the task’s store, mode, product and settings
  • the proxy the task was using, including its login, so we can repeat the run
  • the last lines of the bot’s log
  • your Discord name and ID, so we know whose bot it was
  • the bot’s version and your Windows version

Email addresses and card numbers are taken out before it’s sent, and your saved profiles are not attached.

When the bot closes by itself, or won’t open at all, you can’t reach Send logs. Windows writes down why a program closed, and Event Viewer is where you read it.

Event Viewer with Application picked under Windows Logs, a red Error row selected, its details underneath and the Copy menu on the right

  1. Open the Start menu, type Event Viewer and open it.

  2. In the left panel, open Windows Logs and click Application, marked 1 in the picture.

  3. In the list, find a red Error from the time the bot closed, marked 2. The newest entries are at the top. Its Source is .NET Runtime or Application Error.

  4. Click the row. The box underneath, marked 3, shows what happened. An entry about the bot names yoghurtbot.exe near the top.

  5. On the right, click Copy, marked 4, then Copy Details as Text. Paste it to staff in Discord.

An entry about the bot looks like this:

The details of an error entry. The first line reads Application: yoghurtbot.exe

If no entry names yoghurtbot.exe at that time, Windows didn’t record a crash. Go back to The bot won’t open.

Everything the bot saves lives in one folder. Paste this into the File Explorer address bar to open it:

%APPDATA%\yoghurtbot.io
  • Directoryyoghurtbot.io/
    • yoghurtbot.db your profiles, proxies, tasks and history
    • Directorylogs/ log files, opened by Open folder in Settings
      • …
    • Directorycomponents/ the browser engine and location database
      • …
    • Directoryruntime/ files the bot unpacks each time it starts
      • …