[High Priority] Juggernaut is trying to load socket.io from the wrong port.

[Gabriel Benmergui]

I reinstalled my environment yesterday and with the latest version of
juggernaut (2.0.9) is not loading socket.io and hence not making the
channel connections.

I am deploying my webserver at localhost:9292, and serving juggernaut
on localhost:8080. When i connect to the chat, say, localhost:9292/
chat the following happens:

localhost:8080/application.js is loaded properly
:9292/socket.io/1/?t... Not Found.


When i go to localhost:8080, i am able to connect at the chat, and i
can see that :8080/socket.io/1/.. is served.

This didn't use to happen on juggernaut 2.0.3 (previous version i was
using). This is absolutely blocking.

[Alex MacCaw]

Have you tried specifying the 'port' option when instantiating Juggernaut?

--
You received this message because you are subscribed to the Google Groups "Juggernaut 2" group.
To post to this group, send email to juggernaut...@googlegroups.com.
To unsubscribe from this group, send email to juggernaut-for-r...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/juggernaut-for-rails?hl=en.

--

Alex MacCaw

+12147175129
@maccman

http://alexmaccaw.co.uk | http://www.leadthinking.com | http://socialmod.com

[Gabriel Benmergui]

If you mean doing like this :
var jug = new Juggernaut('localhost:8080');
Yes i did.

Is this a socket.io issue or juggernaut?. Just in case this fix is not
prompt, is there a way to install an older version of juggernaut
easily?. I see no tags on the github repo, and no way to install a
specific version with npm.

Regards.

[Nicolas Cavigliano]

Haven't really followed this conversation that closely, but one thing that sticks out is that you need to pass in a hash and not a string to instantiate the Juggernaut object. 

Ie. var jug = new Juggernaut({host: 'localhost', port: '8080'});

I'm using 2.0.3 and everything is fine for me.

[Nicolas Cavigliano]

I think it defaults to localhost:8080 if you don't include any arguments when instantiating as well.

[Alex MacCaw]

Yup, Nic's correct - it looks like you're passing in a string, rather than an options object. 

[Gabriel Benmergui]

That seems to have worked! Thanks.

[bolade mustapha]

Does anyone know if there is any way to implement voice chat or sending images with juggernaut?

Sent from my Windows Phone

---

From: Alex MacCaw
Sent: Wednesday, September 28, 2011 11:03 AM
To: juggernaut...@googlegroups.com
Subject: Re: [Juggernaut-for-Rails] Re: Juggernaut is trying to load socket.io from the wrong port.

Yup, Nic's correct - it looks like you're passing in a string, rather than an options object. 

On Wed, Sep 28, 2011 at 6:52 PM, Nicolas Cavigliano <nca...@gmail.com> wrote:

I think it defaults to localhost:8080 if you don't include any arguments when instantiating as well.

On Wed, Sep 28, 2011 at 10:49 AM, Nicolas Cavigliano <nca...@gmail.com> wrote:

Haven't really followed this conversation that closely, but one thing that sticks out is that you need to pass in a hash and not a string to instantiate the Juggernaut object. 

Ie. var jug = new Juggernaut({host: 'localhost', port: '8080'});

I'm using 2.0.3 and everything is fine for me.

[Alex MacCaw]

Nope, there isn't. 

[Bill Walton]

On Wed, Sep 28, 2011 at 1:44 PM, bolade mustapha <bmus...@hotmail.com> wrote:
> Does anyone know if there is any way to implement voice chat or sending
> images with juggernaut?

Please don't hijack threads. Your question has nothing at all to do
with the question the OP asked. Hijacking a thread makes it much more
difficult for interested parties to find your question / discussion /
answer in the future.

Best regards,
Bill