Re: Channels: starting Daphne in production

Worried I am connecting, but some initial negotiation isn't occurring when I am using Daphne vs. runserver. I even proved this by starting runserver with --noasgi and running daphne by hand on my desktop and I get the same connect/disconnect pattern. I saw this note, but I am not sure why this

Re: Channels: starting Daphne in production

More specifically, it is logging: None - - [12/Dec/2017:20:*06:39*] "WSCONNECTING /ws/" - - DEBUG Upgraded connection daphne.response.HKlOHkryrd!VaSFKIooRZ to WebSocket daphne.response.HKlOHkryrd!XdRRyyAyVn DEBUG WebSocket closed for daphne.response.HKlOHkryrd!XdRRyyAyVn None - -

Re: Channels: starting Daphne in production

Also, curiously, when I use Inmemory, it seems to connect and immediately disconnect. Hopefully my Nginx conf makes sense. location /ws { proxy_pass http://unix:/tmp/daphne.ws; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection

Re: Channels: starting Daphne in production

Yes, using rabbit... CHANNEL_LAYERS = { 'default': { 'BACKEND': 'asgi_rabbitmq.RabbitmqChannelLayer', 'ROUTING': 'toogo.routing.channel_routing', 'CONFIG': { 'url': 'amqp://foo:bar@{0}:5672/%2F'.format(RABBITMQ_NODE), }, }, } This of course

Re: Channels: starting Daphne in production

Hm, that looks to be like logging from asgi_rabbitmq - could you post your settings configuration? And have you tried running with a different channel layer? Andrew On Tue, Dec 12, 2017 at 10:14 AM, Filbert wrote: > Trying to come up with the proper command line to start

Channels: starting Daphne in production

Trying to come up with the proper command line to start Daphne in production. It seems when I start, it heads off into a repeated processing loop, my thought is that it should just be pending on a websocket connection. Using asgi_rabbitmq. daphne -u /opt/daphne.sock --ws-protocol