Server gateway timeout error

rsamikan
Suddenly i am facing Server gateway timeout error.

File "/usr/local/lib/python3.8/site-packages/kiteconnect/connect.py", line 624, in historical_data
data = self._get("market.historical", {
File "/usr/local/lib/python3.8/site-packages/kiteconnect/connect.py", line 817, in _get
return self._request(route, "GET", params)
File "/usr/local/lib/python3.8/site-packages/kiteconnect/connect.py", line 892, in _request
raise ex.DataException("Unknown Content-Type ({content_type}) with response: ({content})".format(
kiteconnect.exceptions.DataException: Unknown Content-Type (text/html) with response: (b"

504 Gateway Time-out

\nThe server didn't respond in time.\n\n")
  • mlearner
    +1 facing below error. Completely blocked.

    Is there a way KiteConnect team can trigger automatic alert (through Email / SMS or App notification) to all Kite API subscribers about such kind of API failures?

    We will not even know if these issues are happening unless tracked manually all the time or if we build our own alert system. Onus falls on Zerodha though to notify about such failures. Please consider this seriously.

    File "/home/ubuntu/.local/lib/python3.8/site-packages/kiteconnect/connect.py", line 624, in historical_data
    data = self._get("market.historical", {
    File "/home/ubuntu/.local/lib/python3.8/site-packages/kiteconnect/connect.py", line 817, in _get
    return self._request(route, "GET", params)
    File "/home/ubuntu/.local/lib/python3.8/site-packages/kiteconnect/connect.py", line 892, in _request
    raise ex.DataException("Unknown Content-Type ({content_type}) with response: ({content})".format(
    kiteconnect.exceptions.DataException: Unknown Content-Type (text/html) with response: (b"

    504 Gateway Time-out

    \nThe server didn't respond in time.\n\n")

    Thanks.
  • mlearner


    I think timestamps appearing on forum threads have gone haywire. I posted above reply at around 9:40 am and the timestamp shows 9:09 am.
  • sujith
    This should be fixed now.
  • mlearner
    @sujith -
    Is there a way KiteConnect team can trigger automatic alert (through Email / SMS or App notification) to all Kite API subscribers about such kind of API failures?

    We will not even know if these issues are happening unless tracked manually all the time or if we build our own alert system. Onus falls on Zerodha though to notify about such failures. Please consider this seriously.

    Please reply.
  • sujith
    You can get all the operational updates here.
    We also send push notifications on the Kite app.
  • mlearner
    @sujith - I meant intimation sent to KiteConnect subscribers in real time (through Email/SMS/WhatsApp notifications) when critical API fails.

    Bulletin link that you shared did not mention anything about Connect API failure that happened yesterday. It mentions about Kite Charts. Charts can have pure UI issue as well and Connect APIs can continue to function absolutely fine in those cases. How do we differentiate?

    Point is, there is no real time alert mechanism unless subscribers build their own. Also Kite app notifications come quite late.

    I suggest to seriously look into this value addition so that KiteConnect subscribers can at least be alerted in real time. Whole objective of algos is to reduce dependency on screen time.
  • sujith
    Charts are powered by the same backend, so if Kite charts are broken then historical data is also broken.
    Kite app and web are just other client-side apps that use Kite Trade.
    All operational updates are provided on the bulletin, you may even use an RSS feed.
    We don't delay sending notifications on the app.
    As per reports, people tend to ignore or miss emails, So app notifications are a better way of communicating in this case.
  • vikashbucha
    Receiving the following today for the kiteconnect API.
    Fatal error: Uncaught NetworkException (504) 'Gateway timed out'
  • rakeshr
    Fatal error: Uncaught NetworkException (504) 'Gateway timed out'
    Can you paste debug request log for this error?
    Which API request was it?
Sign In or Register to comment.