-
-
Notifications
You must be signed in to change notification settings - Fork 804
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
WSDISCONNECT immedialty after connecting #972
Comments
Does it work without SSL? |
You should also set |
@andrewgodwin yes @matthiask I tried that a bit later, still does'ntwork. thanks |
Then it sounds like it might be a certificate problem or similar with your browser, given that it fails with both nginx and daphne? Is the certificate you're using issued for the right hostname and trusted? (the browser won't prompt you to skip a certificate if it's doing a websocket to a new port). I'm also curious to know what you get in terms of scope/messages through to your consumer - would be good to add some logging there. I don't think this is a channels problem, though, given that the Channels side successfully handshakes (as it gets to |
I managed to make it work, it was an issue with nginx and/or using ReconnectingWebSocket. here's my whole working conf:
daphne
js
|
I tried to make run the tutorial from the docs on my production server, using ssl.
After a few hours i managed to get a connection but it instantly disconnects :
my stack is
I have the exact copy paste of the code from the tutorial, except for this part in room.html
and here is my nginx conf
I run daphne with
daphne -u Daphne.sock Groover.asgi:application -v 3
I also tried bypassing nginx and using
sudo daphne -e ssl:8443:privateKey=/etc/letsencrypt/live/groover.co/privkey.pem:certKey=/etc/letsencrypt/live/groove.co/fullchain.pem Groover.settings:CHANNEL_LAYERS -u Daphne.sock
but i had the same results.
The front break with the message
Chat socket closed unexpectedly
with the error code 1011 (Internal Error) and no reason.The text was updated successfully, but these errors were encountered: