Our Kite Connect app was receiving live ticks and placing live orders through Friday, 30 Oct 2026. On Monday, 2 Nov, the WebSocket stopped connecting.
The app is a paid Kite Connect app. We restarted the VPS and completed a fresh login through our application. No other engine or script generated a Kite Connect session afterward.
Using the same saved API key and access token:
- `/user/profile` succeeds. - `/quote/ltp` succeeds. - A standalone `KiteTicker` 5.2.2 connection fails with HTTP 403. - A raw WebSocket upgrade to `wss://ws.kite.trade` using the documented `api_key` and `access_token` query parameters also returns HTTP 403: `{"status":"error","message":"Authentication failed."}`
The failure occurs during the handshake, before any instrument token or subscription message is sent. So this does not appear to be an instrument-token issue.
Could someone advise why the WebSocket authentication is rejected when REST profile and LTP requests work with the same credentials? Is there an app/session mapping or WebSocket-specific permission that should be checked?
I can provide the exact timestamp and VPS source IP privately if needed. I will not post the API secret or access token publicly.
We are also observing intermittent WebSocket disconnections today around similar timestamps. Here are the logs from our end:
10:12:20 — Closed | 10:12:22 — Reconnected (Duration: 2s)
11:04:52 — Closed | 11:05:05 — Reconnected (Duration: 13s)
11:06:40 — Closed | 11:07:05 — Reconnected (Duration: 25s)
Could you please check if there were any network or server-side drops during these windows?
Thanks