Login Issues - Help?

Alpaca Trading
23

Everyone, the login issue after creating a new account has been resolved. If you were not able to log in, try again. Please post back if you are still having issues. Again, apologies for the inconvenience.

@Micah_Wright The problem you seem to be having is different. I see you created a separate post here and I’ll respond there.

24

I just created a new account, and I am having this same problem. I have gone through the authentication and received an email saying my brokerage account is approved and ready. But when I try to logon, I briefly see a logged in dashboard, but this immediately disappears and takes me back to the login screen. I have tried two browsers (Chrome and Safari), incognito mode, and clearing cookies. Nothing helps. I login and am immediately kicked back to the login screen.

2 Likes
25

I have had an account for a little while now, my trading api broke when attempting to download some forex data and when i try to log into my account I got stuck in this same endless loop of logging in, seeing my homepage, and then immediately being booted out again.

1 Like
26

same issue here just created my account and i go to log in and get sent back to the login page

1 Like
27

I’m having the same problem. Cleared all my cookies, reproduced it on another machine. Something is broken.

28

Same issue. The first time I see a company doing a maintenance and actually making things worse

1 Like
29

I’m having this same issue for the past several login attempts on Chrome and Safari. The issue started yesterday and persists this morning.

1 Like
30

Same issue with my account login as well. Started yesterday late afternoon and continues. Please advise on possible fixes. I too have tried multiple devices, cleared history/cache, etc.

2 Likes
31

I signed up yesterday and am having the same issue reported here. How can I get it resolved?

1 Like
32

@Telcomac99 Currently, there is system maintenance going on. Check out the details here on the status page. That may be the issue in your case. However, the other posts were earlier, and the Alpaca engineering team is looking into the issue.

1 Like
33

Maintenance says complete but this issue still persists. Have tried both laptop and mobile, immediately logs in then out again.

1 Like
34

I’m getting this issue as well:

When looking at network logs, I’m getting a 401 to the paper trader upon successful login, and subsequently a 400 bad request to AWS cognito - So I’m assuming its an issue with the AWS authentication flow - just fyi.

I took the time to grab the HAR files from my login sessions and had Claude read through them with RCA in mind. Maybe would be helpful maybe not:

Title: Logged out immediately after login — caused by 401 on paper account portfolio/history
endpoint

Summary: Every login to app.alpaca.markets succeeds, but I’m bounced back to the login screen
within ~1 second. HAR captures show the cause: a single API call returns 401 and the frontend
treats it as an expired session and force-logs me out.

Details from HAR capture (2026-07-11, ~14:54 UTC):

  • Cognito authentication (InitiateAuth → RespondToAuthChallenge ×3 → GetUser), the
    authx.alpaca.markets token exchange, and ~25 dashboard API calls (accounts, details, margin,
    positions, orders, watchlists) all return 200.
  • Exactly one request fails:
    GET /internal/paper_accounts/<paper_account_id>/portfolio/history?start=0001-01-01T00:00:00Z&period
    =1D&intraday_reporting=continuous → 401 {“code”:401,“message”:“unauthorized”}
  • ~100ms after the 401, the app calls Cognito RevokeToken and navigates away from the dashboard —
    i.e., the frontend deliberately logs the session out in response to the 401. Reproduces on every
    login. (Side effect: because the refresh token gets revoked on each forced logout, other
    tabs/remembered sessions subsequently fail token refresh with a Cognito 400
    NotAuthorizedException.)

What I ruled out (by replaying requests with the same Bearer token from the capture):

  • Not a Cognito/login problem: every Cognito call in the capture returns 200.
  • Not an invalid/expired token: the failing request carries the byte-for-byte identical
    Authorization header as the sibling requests that succeed, and the token was well within its
    validity window.
  • Not clock skew / nbf: replaying the same request 3 minutes after token mint still returns 401.
  • Not the odd start=0001-01-01 parameter: minimal params (?period=1D) and a sane start date also
    return 401.
  • Not account state in general: /positions, /orders, /trade_account/margin on the same paper
    account with the same token all return 200.
  • Not the endpoint in general: the live account’s /internal/accounts//portfolio/history returns
    200 with the same token.

Conclusion: The auth layer in front of /internal/paper_accounts//portfolio/history (which
appears to be a different gateway — its CORS headers advertise Apca-Api-Key-Id/Apca-Api-Secret-Key)
rejects a web-session token that every other dashboard endpoint accepts. The dashboard overview
requests that chart immediately on load, and the resulting 401 triggers the frontend’s global
session-expired handler, logging the user out.

Request IDs from the failing calls, in case Alpaca staff can look them up:
58976713d453db237553e200a2f5bf46 (2026-07-11 14:54:29 UTC) and d0bb00c643f720654d1234981dbb1a8a
(2026-07-11 14:44:56 UTC).

1 Like
35

@Dan_Whitnable_Alpaca if I do the following block, using uBlock origin, my login persists and I don’t get logged back out, fyi:

Workaround: blocking that one request client-side (uBlock Origin filter
||app.alpaca.markets/internal/paper_accounts/*/portfolio/history$xhr) should prevent the 401 so the
session survives; the paper portfolio chart just doesn’t render.

36

I’m running into this issue as well, outside of scheduled maintenance windows. I fairly recently signed up, and it gives me hesitancy using this platform moving forward, especially seeing how this issue has been long-running

Is there any update about this from the Alpaca team? I can’t even withdraw funds if I needed to, it’s pretty concerning. I emailed support but have yet to receive a reply

Edit: Workaround posted by @Dave_F works for me as well

2 Likes
37

Same thing here, was also happening last night long before scheduled maintenance about 12 am Eastern.

38

Same issue…bots can connect, but when logging into the website app.alpaca.markets/account/login I get a “Success! logging you in…” then it kicks me back to the login page.

1 Like
39

Same issue here. Haven’t had any issues before yesterday around noon. Brief login then am rerouted back to the login screen.

3 Likes
40

I am also having the same issue

41

Add the AdGuard AdBlocker extension

Add this user rule

||app.alpaca.markets/internal/paper_accounts/*/portfolio/history$xhr

Save.

Now I have page translated it to English and it says User Filter. That’s a rule so it could also be a User Rule or something like this. It should be User and one of these there. You will get an interpreter starting with “1”. There you paste what I gave above. It should work. You might have some cookie issues so consider to delete them

Edit: Consider removing the rule when 401 error is fixed

1 Like
42

Having the same issue here. Literally created my account 20 mins ago and can’t login :pensive_face: