Websocket Errors while Streaming

Is upstox is forcing me to upgrade to “Upstox Plus”? by halting data flow?

Hi @Akshath_48484164

This is not the case. We have checked the logs for your user ID and observed that around 800 connection requests were made for the v3 WebSocket today. The first two requests were successful at 9:14 AM, after which there are no disconnection logs, and all subsequent requests have failed.

Please recheck your implementation, as we do not see any disconnection from our server side.

Thanks!

1 Like

@Ketan Why I am getting the error , even though I have closed connection in code ?

@Ketan what about my case. I terminated my app. Stopped completely. From upstox github. I’m running v3 node code. Still it is showing as 403

@Ketan can u post a code to close the connection over here. I am sure I am closing connection but just to second your case, I want to cross verify.

@Akshath_48484164 is problem solved for you ?

I am getting exactly same error.

read the post.

Sorry I am not getting you. I have gone through entire post.

https://community.upstox.com/t/error-in-connecting-to-ticker/7991

Ok I got it. My internet connection got bad and script was running at that point. "Yes, that is what I do. But this time my internet connection got disrupted. So it was not possible to close the connection. "

But in this case what I do ? I can’t close the connection which is ended at my end but open at server end. @Akshath_48484164 @Ketan

I Read the post, quite insightful, I checked all these network connections from my EC2 instance. Right now, there are no feeder connections from this instance to UPSTOX. Still when I try and launch a feeder instance I am getting a forbidden error…and seeing that so many users reported this issue today, it leads me to believe that this issue might be arising from Upstoxs’ Side and might be from some users on their side based on their implementation. I am experimenting with a few more things as now the market is closed and I can play around but it would be great if we get some clarity from UPSTOX or some functionality to distinguish the various connection and able to purge it from our side because if this issue persists, we won’t have control over the connections we are making and when we log a disconnect and the server doesnt and we are unable to make new connections.

1 Like

@Raghav_35590666 Many of them reported the same issue today. This might be the upstox issue only.

Can you let us know the issue?
@Pradeep_Jaiswar

Last time I checked I am still having this error; I have completely restarted my EC2 Instance and tried to make the feeder connection but still got the forbidden error. My application was completely affected today.
Now, I’m worried if this connection state is not restored properly on the server by tomorrow, it might lead to an outage tomorrow as well.

@Raghav_35590666 @LOKESH_VEN_1850972 @yuvika_9347091 @Akshath_48484164

We have found an issue on our side related to ungraceful shutdowns from the client side (such as internet disconnections), where the connection count on our servers is not being updated properly.

This should be fixed soon.

Also, just to add — all connections from our servers are cleared at 4:00 AM every morning, so by tomorrow, you should have zero active connections and should be able to connect properly.

We understand and apologize for the inconvenience caused.

Thanks!

2 Likes

Thanks for the clarification @Ketan & Team. Hope it gets fixed soon :grinning_face_with_smiling_eyes: