Why Autoview shows "Disconnected" and how to reconnect
Seeing "Disconnected" is alarming the first time. It looks like everything stopped. In most cases it didn't. That status belongs to the Chrome extension, and it describes one thing: whether the extension is currently in sync with your Autoview account. It is not a report on your trades, your exchange, or the webhook platform.
This guide explains what the state actually means, what keeps running while you see it, and the handful of steps that clear it.
What "Disconnected" actually means
The Chrome extension needs to stay connected to your Autoview account. That link is how your subscriptions and settings stay synchronized to the account you signed in with. When the link drops, the extension shows "Disconnected" until it syncs again.
Here is the part people miss. The state is a sync indicator, not an outage. Reconnect when you're able and your information synchronizes back up. One important detail from the way subscriptions sync: a disconnect only affects new subscriptions waiting to register. Subscriptions that are already active remain available for trading on the extension while you're disconnected. If you just paid or just added an exchange, that is the case that needs a reconnect to sync through.
The webhook platform doesn't have this state
This is the correction worth internalizing. "Disconnected" is an extension concept. The webhook platform is not the extension.
The platform runs on our servers. When an alert sender posts to your webhook URL, the server validates the hook, finds the API keys linked to it, and dispatches the order to your exchange. No browser is involved. Nothing on your machine has to be awake. It accepts a POST from any sender: TradingView, TrendSpider, a Python script, a cron job. TradingView is one possible sender, not the only one.
So if your automation lives on the webhook platform, an extension showing "Disconnected" on some other machine has no bearing on it. The platform keeps executing. The two surfaces are independent. Compare them on the platforms page if you're not sure which one your strategy runs on.
Reconnect and refresh the extension
If you are on the extension and want the sync back, work through these in order.
Reconnect your account
Open the extension and sign back in to your Autoview account. Once the link re-establishes, the status clears and any new subscriptions sync through. If you recently switched computers, sign in with the same account you used before so your subscriptions follow you.
Refresh the extension
If it needs a refresh, go to the chrome://extensions page, then disable and re-enable Autoview. That is the manual reset. You can also have it refresh on a schedule by setting an interval on your Autoview settings page.
A scheduled refresh is usually only worth it under one specific load: many commands packed into a single alert, fired every minute. Chrome itself can hit RAM issues and memory leaks under that pattern. If you see the extension fall behind, build a backlog, or crash Chrome, a periodic reset keeps it healthy. If you aren't running that kind of volume, you probably never need it.
Check Chrome's Memory Saver. Chrome ships a Memory Saver feature, on by default, that frees RAM by putting inactive tabs to sleep. Helpful for casual browsing, bad for a trading extension: a sleeping tab can delay or drop the work the extension was doing. Find it in Chrome's settings under Performance and either turn it off on your trading machine or use its exception list to keep your TradingView tabs active.
If you're on a VPS or Linux
A related failure shows up when setting up a VPS or running on Linux: a message about Google payments, sometimes worded as "Google Subscriptions: Could not establish connection. Receiving end does not exist." Those machines don't ship with Google payments support. Open your permissions page in Autoview, scroll to the bottom, and revoke the Google payments permission. If you hold a legacy Google Payments subscription, that one needs a machine that supports it. Still stuck? Confirm Chrome is logged in with the same email you used when you paid.
When "disconnected" is really the exchange
Sometimes the link to Autoview is fine and the order still fails to reach the exchange. That is a different connection problem, and it lives on the exchange side. The clearest example is an IP allowlist mismatch.
Bybit and a growing number of exchanges secure API keys by IP address. If the address sending the order isn't on the key's allowlist, the exchange rejects it with:
#10010: Unmatched IP - Please check your API key's bound IP addresses.
The fix is to bind the right addresses to your API key. Find your public address with a lookup service such as ipify, then add it to the key inside the exchange. Two wrinkles to plan for:
- IPv4 and IPv6. Some exchanges support both, and your machine may switch between them mid-session. When both are supported, bind both addresses so a flip-flop doesn't lock you out.
- Dynamic addresses. Residential IPs are typically dynamic. A power outage or modem reset can hand you a new address, which silently breaks a key that was bound to the old one. If orders start failing out of nowhere, re-check your current IP first.
Bybit keeps its own API-key documentation current, so set the binding there following Bybit's own guide. The same idea applies to any exchange that allowlists by IP.
Quick triage
Three questions sort almost every case.
- Are you on the extension or the platform? If the platform, "Disconnected" on the extension is not your problem. The server keeps trading.
- Did you just pay or add an exchange? That new subscription needs a reconnect to sync. Sign back in.
- Did the exchange reject the order with an IP error? That is an allowlist mismatch, not an Autoview link. Re-bind your current IP on the exchange.
Reconnect, refresh, or re-bind. One of those clears it.