☰
›

Connection to Zerodha failed: HTTPSConnectionPool(host='api.kite.trade', port=443)

nandas21
nandas21 edited May 2018 in Python client
What could be wrong here. I am actually using the software written by some one else. So I don't have the code. Please let me know what other details you would need. 
INFO:root:Connection to Zerodha failed: HTTPSConnectionPool(host='api.kite.trade', port=443): Read timed out. (read timeout=7)
Email sent!
INFO:werkzeug:127.0.0.1 - - [14/May/2018 19:09:10] "GET /trade HTTP/1.1" 200 -
----------------------------------------
Exception happened during processing of request from ('127.0.0.1', 53766)
Traceback (most recent call last):
File "SocketServer.py", line 290, in _handle_request_noblock
File "SocketServer.py", line 318, in process_request
File "SocketServer.py", line 331, in finish_request
File "SocketServer.py", line 654, in __init__
File "SocketServer.py", line 713, in finish
File "socket.py", line 283, in close
File "socket.py", line 307, in flush
error: [Errno 10053] An established connection was aborted by the software in your host machine
----------------------------------------
  • nandas21
    nandas21
    This was working fine earlier for me. Even now it is working fine for other people.. can you please help me out.
  • nandas21
    nandas21 edited May 2018
    This is a pykiteconnect timeout, more like a client-side timeout. Can you try on some other network? other network? you mean a different wifi network or a LAN?
  • nandas21
    nandas21
    Tried with LAN, still the same issue
  • nandas21
    nandas21
    Tried with a different wifi network as well. Still the same issue. Can you please help me out. This is urgent.
  • sujith
    sujith edited May 2018
    Can you enable debugging as follows,
    logging.basicConfig(level=logging.DEBUG) in new version of pykiteconnect?
    The above log is not enough for debugging.
    We need more details to know what exactly the issue is.

    You can enable debugging and paste the complete log here.
  • sujith
    sujith
    We need to know which API call is throwing this error.
Sign In or Register to comment.