Hi @Hardik_Varma I am also facing exatly same above 2 issues.
Sometimes, also get the error - "Couldn't parse the JSON response received from the server: Gateway Time-out".
This issue will occur API call response do not have any value. @rakeshr please fix the issue. Dec 5th &6th are expiry days .Server may not handle the load
Today again, the quote api failed multiple times. It is affecting our strategy and causing losses. The issue becomes critical when there is a big movement in the market. Please address these api issues at the earliest.
@sujith@rakeshr today also faced frequent errors as below. Couldn't parse the JSON response received from the server:504 Gateway Time-out. The server didn't respond in time. Request failed (kt-quotes). Please advise.
Starting from 5th Dec 2024 we are getting new type of errors for most of the LTP checking api calls and this is a frequent and daily problem as well. And prior to this date not even a single api call error we used to get for our kite api call.
Below are the sample errors.
error 1: Request failed (kt-quotes). error 2: Couldn't parse the JSON response received from the server: b"
504 Gateway Time-out
\nThe server didn't respond in time.\n\n" error 3: Couldn't parse the JSON response received from the server: b'\r\n502 Bad Gateway\r\n\r\n
502 Bad Gateway
\r\n\r\n\r\n'
getting error for below api calls.
kite.ltp kite.ohlc kite.quote
please note: whenever we get this error we are trying to re-try and most of the time the re-try works fine.. but sometime re-try also throws the same error, then we go with another re-try.
At first place if this error happened then we are missing the timing(till we get success in re-try), so our SCALPING setup is highly impacted. Also we are NOT running any other instance of this API keys.. so it means only one api call is running at any given point of time and we are facing the above error. There is no internet issue from our side as well because we are facing this problem on the AWS server and getting daily error.
Kindly treat this as a HIGH priority because API server issus is not acceptable from ZERODHA like industry top broker.
@sujith I am also facing below issue since 6-Dec-2024. 1. error : Request failed (kt-quotes). 2. error : Couldn't parse the JSON response received from the server: b" 3. Discrepancy : The price returned from (kite.ltp) api call shows random behavior with (10-15 points) variation in prices. I tried to compare the the price with websocket streamed data , where i can see prices are different for same timestamp between ltp api and websocket streamed for same instrument. This discrepancies is leading to false alarm in the algos. Kindly look at the issues on priority. The issue is happening since last 3+ trading days.
Hi @sujith@rakeshr can you let us know about API quotes data, are these snapshots are obtained directly from the exchanges at the time of request? or it is fetching from websocket data from your local server?
I am also continiously facing same problem kt-quotes and Couldn't parse the JSON response received from the server: Gateway server didn't respond in time .
What is the problem coming with your server since last 10 days.
My strategy incurred too much loss because of this. Is your server is not able to handle the load.
Please resposnse ASAP as strategy are loss because of these error. Please suggest we should stop using it till the time it is not resolved
@rakeshr Thanks for confirmation. It is certainly not a one-off incident. As many users have reported, the issue is faced on multiple days especially when the volatility increases. Would like to know whether the issue is permanently fixed ?
Both issues have still not been resolved, even after one week. @sujith@rakeshr "error 1: Request failed (kt-quotes). error 2: Couldn't parse the JSON response received from the server: b"
This raises serious concerns about the dependability of Zerodha's technology.
@rakeshr please fix the issue.
Dec 5th &6th are expiry days .Server may not handle the load
I am also facing exatly same in dotnetkiteconnect library issue on eq & fno data
@rakeshr Looks like this issue is at kiteconnect level. Kindly resolve at the earliest.
Couldn't parse the JSON response received from the server:504 Gateway Time-out. The server didn't respond in time.
Request failed (kt-quotes).
Please advise.
Below are the sample errors.
error 1: Request failed (kt-quotes).
error 2: Couldn't parse the JSON response received from the server: b"
504 Gateway Time-out
\nThe server didn't respond in time.\n\n"error 3: Couldn't parse the JSON response received from the server: b'\r\n502 Bad Gateway\r\n\r\n
502 Bad Gateway
getting error for below api calls.
kite.ltp
kite.ohlc
kite.quote
please note: whenever we get this error we are trying to re-try and most of the time the re-try works fine.. but sometime re-try also throws the same error, then we go with another re-try.
At first place if this error happened then we are missing the timing(till we get success in re-try), so our SCALPING setup is highly impacted.
Also we are NOT running any other instance of this API keys.. so it means only one api call is running at any given point of time and we are facing the above error.
There is no internet issue from our side as well because we are facing this problem on the AWS server and getting daily error.
Kindly treat this as a HIGH priority because API server issus is not acceptable from ZERODHA like industry top broker.
This issue is still occurring every day, including today. Please check and fix it on priority.
Unexpected content type text/html StatusCode: 502, ReasonPhrase: 'Bad Gateway', Version: 1.1, Content: System.Net.Http.HttpConnectionResponseContent, Headers: { Server: cloudflare Date: Wed, 11 Dec 2024 04:30:29 GMT Connection: keep-alive CF-RAY: 8f02bd463895493a-BOM Content-Type: text/html Content-Length: 155 }
I am also facing below issue since 6-Dec-2024.
1. error : Request failed (kt-quotes).
2. error : Couldn't parse the JSON response received from the server: b"
3. Discrepancy : The price returned from (kite.ltp) api call shows random behavior with (10-15 points) variation in prices. I tried to compare the the price with websocket streamed data , where i can see prices are different for same timestamp between ltp api and websocket streamed for same instrument.
This discrepancies is leading to false alarm in the algos.
Kindly look at the issues on priority. The issue is happening since last 3+ trading days.
504 Gateway Time-out
\nThe server didn't respond in time.\n\n" problem and only one kt-quotes issue
so its looks if we have high volatility then only we might face this issue..
@sujith pls fix this issue
What is the problem coming with your server since last 10 days.
My strategy incurred too much loss because of this. Is your server is not able to handle the load.
Please resposnse ASAP as strategy are loss because of these error. Please suggest we should stop using it till the time it is not resolved
often doesnt return anything..but couple of times today morning - got yesterdays close price.
Would like to know whether the issue is permanently fixed ?
Says fixed for kite.ltp returning wrong values
"error 1: Request failed (kt-quotes).
error 2: Couldn't parse the JSON response received from the server: b"
This raises serious concerns about the dependability of Zerodha's technology.