{"action":"created","issue":{"url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/196","repository_url":"https://api.github.com/repos/jrief/django-websocket-redis","labels_url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/196/labels{/name}","comments_url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/196/comments","events_url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/196/events","html_url":"https://github.com/jrief/django-websocket-redis/issues/196","id":157486242,"number":196,"title":"Getting ERR_NOT_IMPLEMENTED","user":{"login":"naglalakk","id":1476867,"avatar_url":"https://avatars.githubusercontent.com/u/1476867?v=3","gravatar_id":"","url":"https://api.github.com/users/naglalakk","html_url":"https://github.com/naglalakk","followers_url":"https://api.github.com/users/naglalakk/followers","following_url":"https://api.github.com/users/naglalakk/following{/other_user}","gists_url":"https://api.github.com/users/naglalakk/gists{/gist_id}","starred_url":"https://api.github.com/users/naglalakk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/naglalakk/subscriptions","organizations_url":"https://api.github.com/users/naglalakk/orgs","repos_url":"https://api.github.com/users/naglalakk/repos","events_url":"https://api.github.com/users/naglalakk/events{/privacy}","received_events_url":"https://api.github.com/users/naglalakk/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2016-05-30T11:39:25Z","updated_at":"2016-05-30T13:15:28Z","closed_at":null,"body":"All of a sudden I'm getting this error\r\n\r\n'ws://46.101.214.177/ws/foobar?subscribe-broadcast&publish-broadcast&echo' failed: Error in connection establishment: net::ERR_NOT_IMPLEMENTED\r\n\r\nStrange thing is that on friday I used the exact same url and it worked.\r\n\r\nThe setup I'm using is the one described here:\r\nhttps://github.com/jrief/django-websocket-redis/blob/master/docs/running.rst\r\n\r\nwhere I have two uwsgi processes running, one for django and one for websockets.\r\nI've seen people mention this error in connection with https but I'm not trying to connect through https.\r\n\r\nI have verified that both uwsgi processes are up and running. This is very likely something connected to my setup but if anyone has experienced this issue before it would be great to know and hear what you did to solve this.\r\n\r\nthank you"},"comment":{"url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/comments/222490433","html_url":"https://github.com/jrief/django-websocket-redis/issues/196#issuecomment-222490433","issue_url":"https://api.github.com/repos/jrief/django-websocket-redis/issues/196","id":222490433,"user":{"login":"naglalakk","id":1476867,"avatar_url":"https://avatars.githubusercontent.com/u/1476867?v=3","gravatar_id":"","url":"https://api.github.com/users/naglalakk","html_url":"https://github.com/naglalakk","followers_url":"https://api.github.com/users/naglalakk/followers","following_url":"https://api.github.com/users/naglalakk/following{/other_user}","gists_url":"https://api.github.com/users/naglalakk/gists{/gist_id}","starred_url":"https://api.github.com/users/naglalakk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/naglalakk/subscriptions","organizations_url":"https://api.github.com/users/naglalakk/orgs","repos_url":"https://api.github.com/users/naglalakk/repos","events_url":"https://api.github.com/users/naglalakk/events{/privacy}","received_events_url":"https://api.github.com/users/naglalakk/received_events","type":"User","site_admin":false},"created_at":"2016-05-30T13:15:28Z","updated_at":"2016-05-30T13:15:28Z","body":"Hi thank you for your reply. I don't think this is due to browser updates because when running locally with the url: ws://127.0.0.1:8080/ws/ connects without issues.\r\n\r\nThe access.log from nginx is giving me similar jargon as one gets when trying to connect to https without the address actually being secured by https:\r\n\r\n178.162.216.30 - - [30/May/2016:09:02:11 -0400] \"\\x80\\x03\\x00\\x04\\x00\\x00\\x00\\x14\\x00\\x00\\x00\\x02\\x00\\x00\\x00\\x04\\x00\\x00\\x03\\xE8\\x00\\x00\\x00\\x07\\x00`\\x00\\x00\\x80\\x03\\x00\\x09\\x00\\x00\\x00\\x08\\x00\\x00\\x00\\x00\\x00\\xEF\\x00\\x00\" 400 181 \"-\" \"-\"\r\n\r\nThere are sites running with ssl protection on the same server. I wonder if this is interference between nginx configs. My nginx config is:\r\n\r\n    server {\r\n         server_name localhost;\r\n         listen 80 default_server;\r\n         location / {\r\n            proxy_set_header X-Forwarded-Host $host;\r\n            proxy_set_header X-Forwarded-Server $host;\r\n            proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;\r\n            include /etc/nginx/uwsgi_params;\r\n            uwsgi_pass unix:/tmp/django.socket;\r\n        }\r\n\r\n        location /ws/ {\r\n            proxy_http_version 1.1;\r\n            proxy_set_header Upgrade $http_upgrade;\r\n            proxy_set_header Connection \"upgrade\";\r\n            proxy_pass http://unix:/tmp/web.socket;\r\n        }\r\n    }\r\n\r\nThe uwsgi config for websockets\r\n\r\n    uwsgi:\r\n        uid: www-data\r\n        gid: www-data\r\n        chmod-socket: 666\r\n        chown-socket: www-data:www-data\r\n        workers: 2\r\n        chdir: /home/donna/kott/beinlina/beinlina\r\n        virtualenv: /home/donna/kott/beinlina/venv\r\n        module: wsgi_websocket:application\r\n        env: DJANGO_SETTINGS_MODULE=config.production\r\n        env: DJANGO_CONFIGURATION=Production\r\n        master: True\r\n        vacuum: True\r\n        gevent: 1000\r\n        http-socket: /tmp/web.socket\r\n        http-websockets: True\r\n        pidfile: /tmp/%n.pid\r\n        daemonize: /var/log/uwsgi/%n.log\r\n        touch-reload: /home/donna/kott/beinlina/uwsgireload\r\n"}}
{"actor":{"display_login":"naglalakk"}}