You enter your credentials in the TradingView desktop app and the sign-in fails, loops, or hangs. These 7 fixes separate an account problem from a local Windows problem and resolve both.
Before changing anything, run one test that splits the problem in half. Open tradingview.com in a normal browser and sign in with the same credentials.
This one test saves you from chasing the wrong fix.
Win+R → %AppData%\TradingView → delete the Cache folder → relaunch. A corrupted session can trap the app in a sign-in loop.*.tradingview.com. Add an allow rule in Windows Defender Firewall if sign-in requests are being blocked.First check whether the same credentials work at tradingview.com in a browser. If the browser login also fails, it's an account issue (wrong password, or account locked) — reset your password. If the browser works but the desktop app doesn't, it's a local issue: a corrupted cache, a wrong system clock, or a firewall or VPN blocking the sign-in request.
Yes. Sign-in relies on secure tokens and TLS certificates that are time-sensitive. If your PC's clock is wrong by more than a few minutes, authentication fails silently. Right-click the Windows clock, choose Adjust date and time, and enable Set time automatically.
Yes. Some VPNs route or inspect traffic in a way that breaks the desktop app's sign-in request. Disconnect the VPN, sign in, then reconnect. If it breaks again, the VPN is incompatible — sign in with it off.
Close the app, open %AppData%\TradingView in File Explorer, delete the Cache folder, and relaunch. A corrupted session cache can leave the app stuck on a sign-in loop; clearing it forces a fresh login.
A rejected two-factor code is usually a clock-sync problem on the device running your authenticator app. In the authenticator app's settings, sync the time. Also confirm you're entering the current code — they expire every 30 seconds.