noname

Results 11 comments of noname

401 error seems to be authorization issue. Its working fine for me. ![image](https://user-images.githubusercontent.com/14261211/155053710-bc4020f9-bc16-4a0f-90b8-d47899441ce3.png)

Can you check header - from this point to see if it has access token ![image](https://user-images.githubusercontent.com/14261211/155407740-de42d44d-0f92-4ec9-86dd-6373e08a11e4.png) link in my case: ![image](https://user-images.githubusercontent.com/14261211/155408121-3ad57875-4316-4c19-b9a0-a980d30aedfb.png)

always use WebSocket's to get Realtime data as most brokers will have restrictions on number of pings you can make.

@Anirudh-1213 i think Zerodha is forcing to use TOTP from Sep 23rd so you need to use TOTP code as mentioned in defect 45. (https://github.com/jugaad-py/jugaad-trader/issues/45) https://support.zerodha.com/category/your-zerodha-account/login-credentials/login-credentials-of-trading-platforms/articles/enable-device-lock

were you able to resolve the issue?

@avlsi it's because console class expects 'x-csrftoken' in header. so add below 2 lines in Console class ![image](https://user-images.githubusercontent.com/14261211/219910043-e0664ba0-b9cb-4485-9856-db97d02e63f8.png)

looks like login session didn't execute correctly.

Hello @vijay-arwapally , I think you need to apply 2 changes. 1. ![image](https://user-images.githubusercontent.com/14261211/182043705-fa9e4907-2bf7-4c54-8670-776b3514aa99.png) replace with import urllib.parse ![image](https://user-images.githubusercontent.com/14261211/182043656-63b4ecad-9e04-4cc9-ada8-50c6b0fc32a0.png) 2. In the python package of zerodha - KiteTicket class / file...

Its working for me.. I just updated Kite to latest version without any modification to enc_token. def on_ticks(ws, ticks): # Callback to receive ticks. print(ticks) #print(kws.is_connected()) logging.debug("Ticks: {}".format(ticks)) def on_connect(ws,...

@ashishanand7 if this has not resolved, then try these steps - https://github.com/jugaad-py/jugaad-trader/issues/44#issuecomment-1200493371 > this issue persists. i tried to fix but going nowhere.