Troubleshooting

Fast triage, common fixes, and exactly where to look when the HUD says “no”.

Fast triage (2 minutes)

When something looks wrong, don’t guess. Use the HUD to confirm the system’s heartbeat and the exact veto reason.

  • System Health: check Exit code, Last cycle, and Last scan packet.
  • Feed freshness & gaps: ensure tick age is near-zero and gap rate is low.
  • Order Book: confirm Bid/Ask are updating and spreads aren’t blown out.
  • Execution: if a trade didn’t place, look for the veto (spread, lock, position exists, cooldown, licensing).
Re-run Setup checks Read Modes

Golden rule

If the HUD shows a veto, believe it. Fix the condition first (spread/feed/lock/licensing), then scan again.

  • Wide spread veto? Switch to Lair and wait for normal spreads.
  • Feed stale? Fix MT5 connection before doing anything else.
  • Auto loop confusion? Go Home stops it immediately.

Common problems & exact fixes

Open the panel below that matches what you’re seeing. Each item is written to match how Goldzilla actually behaves (vetoes, locks, loops, and MT5 realities).

This usually means the scan found a setup but execution was vetoed or MT5 rejected the request.

  • Check the HUD for a veto reason: WIDE_SPREAD, COOLDOWN, HAS_OPEN_POSITION, LICENSE, or LOCK.
  • Confirm MT5 is logged in, AutoTrading is enabled, and the symbol is XAUUSD (exact broker naming can vary).
  • Confirm there is no existing position that blocks a new one (Goldzilla is conservative by design).

If your spread exceeds the configured cap, Goldzilla will intentionally refuse to trade. This is a safety feature, not a bug.

  • Wait for spreads to normalize (session transitions and news are common causes).
  • Use Lair when conditions are messy (it’s designed as the safer fallback).
  • Verify the broker is quoting the expected decimals (spread units can be “points” vs “pips”).
  • Confirm Auto Loop ON is visible and “Last cycle boundary” updates.
  • If it starts then stops: check for a crash/exit code and read the latest server log output.
  • If you need to stop immediately: use Go Home (it cancels the loop and returns to manual).
  • Restart MT5 and confirm the chart is receiving live ticks.
  • Confirm the backend can connect to MT5 (terminal running on the same machine/user session).
  • Firewall/VPS: allow local connections and keep MT5 running while Goldzilla runs.

This is typically a front-end connection hiccup (EventSource/SSE) or a backend endpoint restart.

  • Hit Sync HUD (then refresh the page if needed).
  • Confirm the backend is still running (uvicorn terminal still active).
  • If using a reverse proxy/VPS, ensure it supports server-sent events without buffering.

Goldzilla uses lock files to prevent duplicate execution. If a process crashes, a stale lock may remain.

  • Close any duplicate terminals running Goldzilla scripts.
  • If you’re sure nothing is running, remove the lock file and retry.
  • Then scan again and confirm “Last cycle boundary” updates normally.
  • Open License & activation and click Activate / Refresh.
  • Confirm your tier supports the action (Trial vs Pro vs Pro+).
  • If machine binding changed (new PC/VPS), re-activate the key on this machine.
  • Verify the webhook URL is present and saved correctly.
  • Make sure your tier includes Discord alerts (if your build enforces tiers).
  • Check server logs for HTTP errors (401/403/404) when sending alerts.
  • Run MT5 as the same Windows user that runs Goldzilla.
  • Ensure the terminal is logged in and not stuck on a broker dialog.
  • Restart MT5, then restart the backend service.
  • Copy the System Health dump (Exit code, feed, spreads, timestamps).
  • Note your mode + action (Scout/Slay/Go Hunting/Bank Gold).
  • Include the last ~30 lines of backend logs around the event.

Need a clean baseline before you hunt?

Re-check MT5 connectivity, verify feed health, and start in Lair until conditions are stable. Then move up with confidence — and keep the HUD open.

Read the Setup Guide