☰
›

ERROR:main:Error fetching account balance: HTTPSConnectionPool(host='api.kite.trade', port=443):

naveenarya
naveenarya in Python client
ERROR:main:Error fetching account balance: HTTPSConnectionPool(host='api.kite.trade', port=443): Read timed out. (read timeout=7)

I am getting this intermittently , is there any update or issue going on with kite.?

Thanks
Tagged:
  • sujith
    sujith
    We haven't observed any issue at our end. Can you let us know how often do you see this and which endpoint is throwing this error?
    Can you also share the complete stack trace with us by enabling debug logs of pykiteconnect?
    Make sure to remove app and client specific tokens.
  • naveenarya
    naveenarya
    after 10 minutes if i fetch balance again i am consistently getting :

    ERROR:main:Error fetching account balance: HTTPSConnectionPool(host='api.kite.trade', port=443): Read timed out. (read timeout=7)
  • sujith
    sujith
    How often do you fetch balance? Is it after every 10 minutes? At what time did you get the error?
    Can you enable debug logs for pykiteconnect and share complete stack trace?
  • naveenarya
    naveenarya
    Hi Sujith I fetch account balance every 5 seconds, i guess that is with in the api rate limits;


  • naveenarya
    naveenarya
    i sometimes get same error for positions as well
  • rakeshr
    rakeshr
    I fetch account balance every 5 seconds
    It's not recommended to fetch funds APIs so often. It can be an event based request(eg: post placing orders, etc).
  • naveenarya
    naveenarya
    but there was no error earlier, i have been using my code from last 2 years
  • rakeshr
    rakeshr
    HTTPSConnectionPool(host='api.kite.trade', port=443): Read timed out. (read timeout=7)
    We haven't received such feedback about an increase in timeout recently, from any of the users/platforms. Maybe, you can handle this timeout.
  • nish12
    nish12
    I have same issue for last one week, when i trace i can see why
    --- api.kite.trade ping statistics ---
    3222 packets transmitted, 3213 packets received, 0.3% packet loss

    --- google.com ping statistics ---
    3269 packets transmitted, 3269 packets received, 0.0% packet loss
  • Nivas
    Nivas
    @nish12 You may refer to the similar discussion here.
Sign In or Register to comment.