-
Notifications
You must be signed in to change notification settings - Fork 35
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket Error #170
Comments
same error! did you found any fix? |
I had to delete some of my Chats to get to work again (I had over 50). Maybe there is a limit or it was a fluke. |
Is there any one who found the solution of how to solve the problem with the socket error pleasee !! Thank you |
@kuladeepperumalla @emmanuel-omegaalexis @HaAymar @alamorre |
@HridoyHazard I deleted the chats and created new ones, I have not seen the error since. I thought was because I had too many chats (each user has over 200 chats each) but I have not been able to confirm that. |
i tried this but still not working...getting the same error. but message is sending to the user but it needs to reload to see it from user end @emmanuel-omegaalexis |
did you solve it already? @HridoyHazard |
how to solve this error |
Hi @alamorre having similar problem with one important difference: While ChatFeed is working with the support example ( though I had to increase the timeout to 4000 to get it to work Any suggestions will be much appreciated! |
By ellimination I figured out the websock problem was caused by </React.StrictMode> as soon as I removed it the problem went away. Chat GPT suggests Best Practices Idempotent Side Effects: Ensure that side effects (like WebSocket connections) are idempotent, meaning that initializing or cleaning them up multiple times has no adverse effects. In case you guys are still struggling with this @kuldeepperumalla @emmanuel-omegaalexis @HaAymar @adityaChauhan2510 @adityaChauhan2510 @emmanuel-omegaalexis |
The username and password are correct but I keep getting a websocket error.
WebSocket connection to 'wss://api.chatengine.io/person_v4/?session_token=' failed:
The text was updated successfully, but these errors were encountered: