☰
Login
Signup
Home
›
Python client
Howdy, Stranger!
It looks like you're new here. If you want to get involved, click one of these buttons!
Sign In
Register
Categories
Recent Discussions
Activity
Categories
13.9K
All Categories
0
Incidents
156
Node JS client
40
Go client
793
.Net API client
380
Kite Publisher
537
.Net / VBA / Excel (3rd party)
457
Algorithms and Strategies
998
Java client
1.1K
API clients
404
PHP client
4K
Python client
347
Mobile and Desktop apps
1.4K
Market data (WebSockets)
3.3K
General
In this Discussion
November 2018
rakeshr
November 2018
muthu0101
November 2018
sujith
WebSocket connection upgrade failed 403 - Forbidden
muthu0101
November 2018
in
Python client
Just I install kiteconnect using pip install --upgrade kiteconnect, after that I am trying to use the below websocket example
https://github.com/zerodhatech/pykiteconnect#websocket-usage
and I getting this error. I confirmed the api_key is correct and access_token I used the request_token from login return URL.
ERROR:kiteconnect.ticker:Connection error: 1006 - connection was closed uncleanly (WebSocket connection upgrade failed (403 - Forbidden))
ERROR:kiteconnect.ticker:Connection closed: 1006 - connection was closed uncleanly (WebSocket connection upgrade failed (403 - Forbidden))
Process finished with exit code 0
Tagged:
Python Client
WebSocket
sujith
November 2018
Can you let us know which version of pykiteconnect are you using?
Are you passing the right api_key and access_token? It seems fine from our end.
muthu0101
November 2018
Python verision 3.6 and pykiteconnect would be the latest one
muthu0101
November 2018
KiteTicker("your_api_key", "your_access_token") just I replaced the API Key and Request Token that's it right?
rakeshr
November 2018
@muthu0101
You need to replace access_token in second param not request_token.
Go through this documentation
to understand the flow.
muthu0101
November 2018
thanks its working now
This discussion has been closed.
Are you passing the right api_key and access_token? It seems fine from our end.
You need to replace access_token in second param not request_token.Go through this documentation to understand the flow.