Does kite API's and WebSocket support IPv6 Network? As I have submitted my application to app store it got rejected saying that they are not able to load Kite login page. Apple people have reviewed the application around 1 AM to 2 AM IST midnight. Is there any downtime for kite at that time? They also mentioned that they will be testing in IPv6 only.
Hi, Post-midnight OMS doesn't accept any request since BOD process will go on till around 6:00 AM IST. You need to mention that on itunesconnect while uploading new build.
Downtime is for OMS not to login's right? I am unable to login to kite midnights. Or if any response from the server that systems are under maintenance.
Could you please let us know if Websockets support IPv6 ?
On an IPv4 network ./websocat.x86_64-unknown-linux-musl ws://ws.kite.trade websocat: WebSocketError: WebSocketError: Received unexpected status code (400 Bad Request)
On an IPv6 only network /tmp/websocat.x86_64-unknown-linux-musl ws://ws.kite.trade websocat: WebSocketError: Network unreachable (os error 101) websocat: error running
*Edit for a working websocket server on IPv6 only network
/tmp/websocat.x86_64-unknown-linux-musl ws://echo.websocket.org websocat: WebSocketError: WebSocketError: Redirected (301 Moved Permanently) to https://echo.websocket.org/ websocat: error running
Thank you for taking a look here. If you could see above ws://ws.kite.trade returns Network unreachable on an IPv6 only network while a different server responds back.
I have been able to request CSVs etc. on an IPv6 only network from kite( for e.g. api.kite.trade) but websocket is unreachable. Even name resolution fails for IPv6 while for other domains it works
I could show the exact output if needed(it'll take some time as I've stopped using IPv6 only network for now) but if you see above resolution doesn't return an IP to point to. Am I missing something here ?
Hi Team, Can we at least get an ack on this? And if possible, some tentative timelines on when we can expect this to be implemented? Have been following it up for quite some time now and there has been very little engagement here.
Thank you for the update @sujith , I was hoping to see support for IPv6 only networks. Is there a possibility/plan to include it in the long run? With a yes/no to this query I guess we're good to close this thread.
Post-midnight OMS doesn't accept any request since BOD process will go on till around 6:00 AM IST. You need to mention that on itunesconnect while uploading new build.
Could you please let us know if Websockets support IPv6 ?
On an IPv4 network
./websocat.x86_64-unknown-linux-musl ws://ws.kite.tradewebsocat: WebSocketError: WebSocketError: Received unexpected status code (400 Bad Request)
On an IPv6 only network
/tmp/websocat.x86_64-unknown-linux-musl ws://ws.kite.tradewebsocat: WebSocketError: Network unreachable (os error 101)
websocat: error running
*Edit for a working websocket server on IPv6 only network
/tmp/websocat.x86_64-unknown-linux-musl ws://echo.websocket.orgwebsocat: WebSocketError: WebSocketError: Redirected (301 Moved Permanently) to https://echo.websocket.org/
websocat: error running
A ping on this thread. Did you get a chance to check this ?
Thank you for taking a look here. If you could see above ws://ws.kite.trade returns Network unreachable on an IPv6 only network while a different server responds back.
I have been able to request CSVs etc. on an IPv6 only network from kite( for e.g. api.kite.trade) but websocket is unreachable. Even name resolution fails for IPv6 while for other domains it works
nslookup api.kite.trade
Server: 10.255.255.254
Address: 10.255.255.254#53
Non-authoritative answer:
Name: api.kite.trade
Address: 104.16.33.50
Name: api.kite.trade
Address: 104.16.34.50
Name: api.kite.trade
Address: 2606:4700::6810:2232
Name: api.kite.trade
Address: 2606:4700::6810:2132
nslookup ws.kite.trade
Server: 10.255.255.254
Address: 10.255.255.254#53
Non-authoritative answer:
ws.kite.trade canonical name = kite-prod-ticker-connect-1378672944.ap-south-1.elb.amazonaws.com.
Name: kite-prod-ticker-connect-1378672944.ap-south-1.elb.amazonaws.com
Address: 3.109.126.236
Name: kite-prod-ticker-connect-1378672944.ap-south-1.elb.amazonaws.com
Address: 52.66.86.90
I could show the exact output if needed(it'll take some time as I've stopped using IPv6 only network for now) but if you see above resolution doesn't return an IP to point to. Am I missing something here ?
Best regands [url=https://mazzani.pl]
A ping on this thread. Do we have any update?
A ping on this thread. If I can present any other results / am missing something completely please do let me know.
Any update on this thread if you got a chance to look at it? I can still reproduce this at my end
wss://ws.kite.trade ( Fails with IPv6 ) ws://echo.websocket.org ( A random test site ) wss://api.kite.trade ( Given, that api.kite.trade does not support websocket protocol, it still responds with a HTTP 200 on both sides)
Can we at least get an ack on this? And if possible, some tentative timelines on when we can expect this to be implemented? Have been following it up for quite some time now and there has been very little engagement here.
We have informed the team to take a look at this. It should be fixed in a couple of weeks.
The team suggested to use dualstack network to resolve this issue.