☰
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.8K
All Categories
0
Incidents
154
Node JS client
40
Go client
793
.Net API client
378
Kite Publisher
537
.Net / VBA / Excel (3rd party)
457
Algorithms and Strategies
993
Java client
1.1K
API clients
404
PHP client
4K
Python client
346
Mobile and Desktop apps
1.4K
Market data (WebSockets)
3.3K
General
In this Discussion
December 2018
Imran
December 2018
sujith
December 2018
prashant11
December 2018
shortwire
December 2018
naz
Getting error while running web sockets
vatayush
December 2018
in
Python client
Hi, when i try to run web socket with the reference code given on github i am getting the following error:
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))
I know that i am correctly passing the access token and the api key, because the same tokens are working for placing orders.
Please look into it
Thanks,
Ayush
Tagged:
Python Client
WebSocket
error
naz
December 2018
Same Error. And I have also checked that i am correctly passing the access token and the api key.
Please advise asap.
shortwire
December 2018
May be tick server is not available.
@sujith
can you pls confirm if this is down for maintenance?
prashant11
December 2018
Still the same issue persists.
@sujith
please help us here.
sujith
December 2018
We were doing some maintenance during the weekend. It should be fine now.
Imran
December 2018
hii
@sujith
tried running the WebSocket code the issue still persists.
sujith
December 2018
I just tried and it seems fine. Are you sure you are using a valid access token?
Imran
December 2018
its working fine ..thanks
This discussion has been closed.
Please advise asap.
tried running the WebSocket code the issue still persists.