Getting error while streaming instruments

viraltaretia

Go Client I am getting below error while subscribing to below instruments... Where as getting proper ticks in other instruments. I have got these instruments from

err := ticker.SetMode(kiteticker.ModeFull, []uint32{3329, 5633, 6401, 25601, 40193, 41729, 54273, 60417, 67329, 70401, 78081, 81153, 94977, 98049, 101121, 103425, 108033, 108801, 112129, 114433, 119553, 121345, 131329, 134657, 140033, 149249, 160001, 160769, 163073, 173057, 177665, 185345, 193793, 197633, 211713, 225537, 232961, 234497, 240641, 245249, 261889, 299009, 300545, 306177, 315393, 320001, 325121, 340481, 341249, 342017, 345089, 348929, 356865, 359937, 387073, 387841, 403457, 408065, 414977, 415745, 424961, 462849, 486657, 492033, 511233, 519937, 558337, 579329, 582913, 589569, 593665, 617473, 625153, 630529, 633601, 637185, 648961, 676609, 681985, 692481, 720897, 733697, 738561, 758529, 760833, 767233})

Connected
Tick
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x8 pc=0x677aec]

goroutine 31 [running]:
main.onTick(0x719d78, 0x4, 0x10001da01, 0x0, 0xed6474987, 0x9565a0, 0x0, 0xed6472492, 0x9565a0, 0x40d22eaccccccccd, ...)
gokiteconnect-master/examples/ticker/ticker.go:77 +0xcc
github.com/zerodhatech/gokiteconnect/ticker.(*Ticker).triggerTick(...)
gokiteconnect-master/ticker/ticker.go:411
github.com/zerodhatech/gokiteconnect/ticker.(*Ticker).readMessage(0xc000157040, 0xc0001c9e00)
gokiteconnect-master/ticker/ticker.go:469 +0x219
created by github.com/zerodhatech/gokiteconnect/ticker.(*Ticker).Serve
gokiteconnect-master/ticker/ticker.go:354 +0x3f7
exit status 2

also in python client I am getting below error

ERROR:kiteconnect.ticker:Connection error: 1006 - connection was closed uncleanly (WebSocket connection upgrade failed (403 - Forbidden))

Please help here

rakeshr

@viraltaretia

WebSocket connection upgrade failed (403 - Forbidden))

Your authentication is falling. Make sure you are using correct api_key and access_token. Recheck the same. If still facing the issue,paste your websocket code here,we will look to it.

viraltaretia

Thanks @rakeshr.