Troubleshooting

Seeing a 502 Error? Agent Not Loading?

A practical recovery checklist for the most common 502 failures, plus what to send support if it still fails.

If your Heyron page shows 502 Bad Gateway, this usually means your agent service didn't respond in time — not that your account is gone.

Good news: most 502 issues are temporary and recover with a quick reset flow.

Fast recovery (3–5 minutes)

1) Hard refresh the page

Desktop: Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows). Mobile: fully close the app/browser tab and reopen.

2) Try again after 30–60 seconds

Short platform restarts happen. A second attempt often works once the container is awake again.

3) Open your agent from a private/incognito window

This bypasses stale cookies/cache and quickly tells you if the issue is browser-local.

4) Check if it's only one agent

If one agent fails but another opens, the issue is likely isolated to that workspace/config instead of your whole account.

5) Retry from Discord/Telegram (if connected)

If channel replies still work while dashboard fails, your agent may be alive and only web access is degraded.

Quick isolation matrix (find the failing layer fast)

Fails only in one browser: local cache/extension/session issue is most likely
Fails on all browsers but Discord/Telegram still replies: dashboard/web path issue
Fails on web + Discord/Telegram: agent/container startup issue
Fails only on your Wi-Fi, works on mobile data: local network/VPN/DNS filtering issue

What usually causes 502

Container cold start or restart in progress
Temporary upstream outage/load spike
Corrupted browser cache/session state
Workspace startup blocked by a bad config change
Network middleware interference (VPN, ad blocker, DNS filtering, strict corporate proxy)

Extra checks before support (2 minutes)

6) Disable extensions that modify traffic

Temporarily disable ad blockers/privacy tools for your Heyron domain, then retry. These can block websocket or upstream requests and produce 502-like failures.

7) Turn off VPN/proxy and retry

Some VPN/proxy paths timeout or filter required requests. A quick no-VPN retry helps isolate network path issues.

8) Compare Wi-Fi vs mobile hotspot

If hotspot works but home/work Wi-Fi fails, share that detail in your #help post. It narrows diagnosis immediately.

When to contact support

Open #help if any of these are true:

502 persists for more than 10 minutes
You've already tried hard refresh + incognito + retry
The same agent fails repeatedly across devices

Copy/paste this support packet

I'm getting a 502 on my Heyron agent. Agent URL/subdomain: [your link] Started around: [time + timezone] Tried already: hard refresh, waited 60s, incognito, second device Result: still failing / now working intermittently Signup email: [your account email]

Security reminder: never post API keys, tokens, or passwords in #help. Share only your signup email and non-secret diagnostics.

Prevent repeat issues

Keep big prompt/config edits incremental (small changes are easier to recover)
Store important instructions in files (SOUL.md, AGENTS.md, MEMORY.md) so recovery is fast
Use a channel fallback (Discord/Telegram) so you're not blocked if web UI is briefly down

Bottom line: 502 is usually a temporary service response issue. Run the quick checklist, then escalate with a clean support packet if it persists.