-
-
Notifications
You must be signed in to change notification settings - Fork 817
Close code: 1011 (No logging) #1383
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
Comments
Had very similar issue. What was happening for me was in our chat system, when sending a message, connection would close with error 1011 and no error in the logs.
For some reason unknown to me it didn't actually log this error anywhere. But just crashed.
Then I could see the error. Hopfully this helps you or someone in the future. |
This is the first issue. It would be nice for this to bubble up. @CylonOven Could you put a minimal project together showing your set up so we can work out what would need to change there? (Ta!) |
The missing logs can be related to django-commons/django-debug-toolbar#1300 |
Just wanted to contribute to this issue, how I caused it. ;) and fixed it. I am using async. Its easy to forget you need to convert certain calls into |
Hi.
I'm trying to configure channels, with redis layer, i'm well connected to the channels with a source-client.
After some messages correctrly sended, the channel fails and cut the communication.
Send: 1011 close_code and no more information....
What can i do?
The text was updated successfully, but these errors were encountered: