wandenberg / nginx-push-stream-module

A pure stream http push technology for your Nginx setup. Comet made easy and really scalable.
Other
2.22k stars 295 forks source link

Pushed messages does not appear via WebSocket #14

Closed MWent closed 12 years ago

MWent commented 12 years ago

Hello,

iam using nginx v1.0.11 and have a weird problem with WebSockets (on both Firefox and Chrome).

After i publish messages via curl (from bash like one of these examples in readme) they dont appear on subscriber, long-polling/stream/event works perfectly..

The weird thing is when i close nginx (/etc/init.d/nginx stop) the subscribes get the messages afterwards.

config for websocket is simple:

    location ~ /ws/(.*) {
            push_stream_websocket;
            set $push_stream_channels_path $1;
            push_stream_message_template                "{\"id\":~id~,\"channel\":\"~channel~\",\"text\":\"~text~\"}";

            push_stream_ping_message_interval           10s;
    }

iam using the pushstream.js from the package...

state is on all 'connected' and publisher gets the correct amount of current subscribers

wandenberg commented 12 years ago

Hi,

did you tried to use the chat example on http://www.nginxpushstream.com/chat.html ? If not, take a look on that to see if works on your browser.

If not work tell me the version of your browser. If work may be a problem on your environment, and I will need more information to help you, like a example app you are using, the complete nginx conf where problem occurs, O.S. version and what more information you can give me .

Regards, Wandenberg

MWent commented 12 years ago

well the chat example works - after i compared the js files they seems different - maybe thats why? (i should test that one)

so my workstation looks ok so far (win 7 x64 prof. / ffox & chrome up-to-date)

my server is an debian squeeze vm (2.6.32-6-pve) which runs in a proxmox enviroment - and the proxmox runs on my vmware workstation (using this way before i migrate to my main node)

since iam not familiar with githubs markdown (just regged today..) i used nopaste...

nginx.conf http://nopaste.info/5d3727f314.html

0-default: (server conf) http://nopaste.info/bd9dd477d2.html

html file (also from examples): http://nopaste.info/2b0a867d9a.html

nginx build: nginx version: nginx/1.0.11 built by gcc 4.4.5 (Debian 4.4.5-8) TLS SNI support enabled configure arguments: --prefix=/etc/nginx \ --conf-path=/etc/nginx/nginx.conf \ --error-log-path=/var/log/nginx/error.log \ --http-client-body-temp-path=/var/lib/nginx/body \ --http-fastcgi-temp-path=/var/lib/nginx/fastcgi \ --http-log-path=/var/log/nginx/access.log \ --http-proxy-temp-path=/var/lib/nginx/proxy \ --http-scgi-temp-path=/var/lib/nginx/scgi \ --http-uwsgi-temp-path=/var/lib/nginx/uwsgi \ --lock-path=/var/lock/nginx.lock \ --pid-path=/var/run/nginx.pid \ --with-debug \ --with-file-aio \ --with-http_addition_module \ --with-http_dav_module \ --with-http_flv_module \ --with-http_geoip_module \ --with-http_gzip_static_module \ --with-http_image_filter_module \ --with-http_perl_module \ --with-http_random_index_module \ --with-http_realip_module \ --with-http_secure_link_module \ --with-http_stub_status_module \ --with-http_ssl_module \ --with-http_sub_module \ --with-http_xslt_module \ --with-ipv6 \ --with-sha1=/usr/include/openssl \ --with-md5=/usr/include/openssl \ --with-mail \ --with-mail_ssl_module \ --add-module=/usr/src/nginx-1.0.11/nginx-push-stream

MWent commented 12 years ago

k, tested the pushstream.js from http://www.nginxpushstream.com/ - still the same problem...

now i used the chat example from misc/examples - hu? it works - i will look more into it...

thanks for supporting fast as lightning

\edit well weird - now it does not work (still the chat example) - only refreshed the page and now i cant get messages or send them..

for chrome the same issue...

The weird thing is - sometimes i get messages, most of the time not.

if i click the send button nothing appears on log as well, after a while i get a debug msg (firebug):

Connection to ws://192.168.159.133/ws/example?_=1327024677613 was canceld while loading. (translated)
...nection = (window.WebSocket) ? new window.WebSocket(url) : new window.MozWebSock... pushstream.js (Line 205)

sometimes after this point it seems to work

mh, at the moment i have these problems also on your hosted example - again with ffox and chrome (which is fresh installed)

wandenberg commented 12 years ago

Hi,

I will take a look on that soon. Please, do one more test for me. Set tcp_nopush to off, and see if it works.

MWent commented 12 years ago

Thanks,

setting tcp_nopush off; did no effects, still the same.

wandenberg commented 12 years ago

Hi,

I used your configuration and html file and every thing works fine. The only changes I did is comment line "include base_config;", because you didn't sent it to me and, add the time when printing the message on html.

I will try to send a print screen on attach, but I don't know if github will accept.

If you can give me access to your server to help you.

Regards, Wandenberg

On Fri, Jan 20, 2012 at 1:19 AM, MWent < reply@reply.github.com

wrote:

Thanks,

setting tcp_nopush off; did no effects, still the same.


Reply to this email directly or view it on GitHub:

https://github.com/wandenberg/nginx-push-stream-module/issues/14#issuecomment-3578625

MWent commented 12 years ago

Hello,

well it seems to be a problem on my system - it worked on my girls laptop / friends computer - both using Win7 + Firefox - even Firefox 8.0 worked...

Tests was done via nginxpushstream.com/chat.html - still wondering why it does not work on my system, (Chrome + Firefox).

Btw. sry that i forgot to include base_config file but there are only some default deny's.

Thanks for you help, i will get in contact if i find out what the hell the problem is.. so long it can be closed i guess..