# Alpaca login flasing dashboard then logging out **URL:** \ **Category:** Alpaca Account Troubleshooting\ **Created:** [July 11, 2026, 6:32pm UTC](https://forum.alpaca.markets/t/alpaca-login-flasing-dashboard-then-logging-out/19294 "2026-07-11T18:32:42Z")\ **Posts on this page:** 4\ **Page:** 1
**Author:** ![Chris\_Bates](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/chris_bates/32/8506_2.png) [@Chris\_Bates](https://forum.alpaca.markets/u/Chris_Bates)\ **Post date:** [July 11, 2026, 6:32pm UTC](https://forum.alpaca.markets/t/alpaca-login-flasing-dashboard-then-logging-out/19294/1 "2026-07-11T18:32:42Z")
## So using a chrome browser from my mac, I am no longer able to log into the alpaca trading dashboard, was working fine for weeks, now logs in, I see the dashboard for a second, and then logs out. I used claude to debug and here are the findings That’s the smoking gun. Here’s the full sequence the userscript caught: You log in → it goes to the dashboard (`/dashboard/overview` genuinely loads at 18:21:52) → the dashboard fires two authenticated API calls → **both come back `401 {"code":401,"message":"unauthorized"}`** → and ~0.1s later it bounces you to `/account/login`. So the login itself succeeds and mints a token, but **Alpaca’s backend rejects that token with 401** when the dashboard tries to use it. That’s why nothing browser-side fixed it — the handshake works; the server is refusing the authorization. Let me pull the exact endpoint that’s 401’ing (stripping the query string so the tool will show it). Used claude-in-chrome integration Used claude-in-chrome integration Now it’s precise. The failing call is: `GET app.alpaca.markets/internal/paper_accounts/ **58946c69-3597-4f17-8c1f-ad9995da7a15** /portfolio/history` → **401 unauthorized** This is a **paper trading account**. Your dashboard loads, tries to pull the portfolio history for that specific paper account, gets a 401, and the app treats that single 401 as a session failure and logs you out — hence the loop. It’s not your browser and not your credentials; it’s that one paper account’s data being rejected. Let me look at the rest of the requests in that dashboard load to see what _succeeded_ (like the accounts list) so we can tell whether that paper account is stale/orphaned versus a broader server issue. Used claude-in-chrome integration Used claude-in-chrome integration Got it — this fully explains it, and it’s **not your browser, your credentials, or anything you can fix by clearing data.** Here’s the proof, from that same dashboard load: The login and token are completely healthy — Cognito and `authx.alpaca.markets/v1/oauth2/token` all returned 200. And your token is authorized for the paper account (`58946c69…`): on that _same_ account, in the _same_ split second, these all succeeded — - `…/paper_accounts/58946c69…/positions` → **200** - `…/paper_accounts/58946c69…/orders` → **200** - `…/paper_accounts/58946c69…/trade_account/margin` → **200** - `authx…/paper-accounts/58946c69…/client-credentials` → **200** Only **one** endpoint failed: - `…/paper_accounts/58946c69…/portfolio/history` → **401** (and it retried once — you can even see Alpaca fire token-refresh calls to Cognito at 52.6–52.7s trying to recover — still 401). So a single Alpaca endpoint, `portfolio/history`, is returning 401 while every sibling endpoint on the same account with the same token returns 200. That’s a **server-side bug on Alpaca’s portfolio-history service** — not an auth problem. The reason it logs you out is that Alpaca’s dashboard has an over-aggressive global handler: _any_ 401 → “session expired” → refresh-and-retry → still 401 → dump you back to login. One flaky endpoint is nuking your whole session. What this means: - **You can’t fix this from your side** — it’s Alpaca’s. Worth checking status.alpaca.markets and reporting it to Alpaca support with this exact evidence (portfolio/history 401 while positions/orders/margin return 200 for the same paper account). That’s a precise, hard-to-argue bug report. If you want _into_ the dashboard in the meantime, I can extend the Tampermonkey script to intercept that one broken `portfolio/history` response and hand the app a harmless empty result instead of the 401 — that stops the logout trigger and lets the dashboard load (the portfolio-history chart would just be blank until Alpaca fixes their end). Want me to build that workaround? Otherwise, disable the debug script for now and I’ll note this so we can revisit. ---
**Author:** ![Chris\_Bates](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/chris_bates/32/8506_2.png) [@Chris\_Bates](https://forum.alpaca.markets/u/Chris_Bates)\ **Post date:** [July 11, 2026, 6:39pm UTC](https://forum.alpaca.markets/t/alpaca-login-flasing-dashboard-then-logging-out/19294/2 "2026-07-11T18:39:58Z")
My guess is it has something to do with this and a bug introduced in protfolio/history **[Scheduled Maintenance of Sandbox & Production - Sat, Jul 11, 7:00–9:30 AM EDT](https://status.alpaca.markets/incidents/98c5bp9b69kz)** **Completed** - The scheduled maintenance has been completed. Jul 11, 09:27 EDT **In progress** - Scheduled maintenance is currently in progress. We will provide updates as necessary. Jul 11, 07:00 EDT ---
**Author:** ![Amichay\_Doitch](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/amichay_doitch/32/7873_2.png) [@Amichay\_Doitch](https://forum.alpaca.markets/u/Amichay_Doitch)\ **Post date:** [July 14, 2026, 1:48pm UTC](https://forum.alpaca.markets/t/alpaca-login-flasing-dashboard-then-logging-out/19294/3 "2026-07-14T13:48:14Z")
same issue, started after the July 11 maintenance ---
**Author:** ![Dan\_Whitnable\_Alpaca](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.alpaca.markets/dan_whitnable_alpaca/32/1658_2.png) [@Dan\_Whitnable\_Alpaca](https://forum.alpaca.markets/u/Dan_Whitnable_Alpaca)\ **Post date:** [July 14, 2026, 2:00pm UTC](https://forum.alpaca.markets/t/alpaca-login-flasing-dashboard-then-logging-out/19294/4 "2026-07-14T14:00:46Z")
This issue has been resolved. Alpaca is migrating to a different internal authentication structure and several endpoints hadn’t been updated to recognize the new authentication. Paper trading portfolio history was one of those end points. This endpoint is called immediately when opening a paper account to render the equity chart. The end point didn’t authenticate so therefore asked to have the user login again creating an endless loop. The status update can be found [here](https://status.alpaca.markets/incidents/kcj7gd3mmsrx). Apologies for the inconvenience.