Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Already on GitHub? Sign in to your account

unbind directly after initialize #86

Closed
luceos opened this Issue Jan 4, 2013 · 7 comments

Comments

Projects
None yet
3 participants

luceos commented Jan 4, 2013

I've installed rvm, bundler and the gem slanger. Once I connect (no authing whatsoever yet) to the wss the client gets kicked. It never really connects. The logs aren't helpful though:

[[:initialize]]

[[:unbind, :connection]]

There is no response in the browser, just a "pending" message.

Any idea's?

Owner

stevegraham commented Jan 4, 2013

Thanks Daniel, I'll look into this later today/this weekend.

Owner

stevegraham commented Feb 7, 2013

Could this be a SSL issue?

luceos commented Feb 8, 2013

I will try now Steve.

luceos commented Feb 8, 2013

So I disabled the SSL all together, leaving only the keys in place for the startup. However to no avail.

The redis log is also empty. Something that also strikes me is that in the client js I disabled ssl / encrypted connection, but it still connects with wss, how come?

When I compare this version with a working one I see in the console:

slanger.rb: process with pid 8918 started.


    .d8888b.  888                                               
   d88P  Y88b 888                                               
   Y88b.      888                                               
    "Y888b.   888  8888b.  88888b.   .d88b.   .d88b.  888d888   
       "Y88b. 888     "88b 888 "88b d88P"88b d8P  Y8b 888P"     
         "888 888 .d888888 888  888 888  888 88888888 888       
   Y88b  d88P 888 888  888 888  888 Y88b 888 Y8b.     888       
    "Y8888P"  888 "Y888888 888  888  "Y88888  "Y8888  888       
                                         888                    
                                    Y8b d88P                    
                                    "Y88P"                      


Slanger API server listening on port 1338
Slanger WebSocket server listening on port 1337

but nothing more, is that correct?

Hi, im facing the same problem using SSL.

I'm using --cert_chain_file and --private_key_file options and I have configured Pusher.wss_port on javascript and Pusher.encrypted on initializer as well.

Request seem to be using wss:// but they are still shown as "Pending" and Slanger show the message

[[:initialize]]

[[:unbind, :connection]]

Any thoughts?

Thanks for the great job.

nanocity commented May 7, 2013

Quick follow-up, I finally have this working.

I don't know where the issue was exactly and if it is related to Slanger, but maybe someone get here with the same problem.

It turns out that you have to set the Pusher.host value for Javascript client exactly as the certificate CommonName you are using. I set IP instead of domain name so the connection was getting unbound silently.

I found the answer here: http://blog.heidt.biz/blog/2012/07/19/ssl-websocket-proxy-with-stunnel-howto/

Thanks again, for this gem.

Owner

stevegraham commented Jul 18, 2014

Closing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment