Connecting nodejs to ga-bitbot

[GoogleCodeExporter]

Sorry for using the issues to ask beginner questions :S There doesn't seem to 
be an IRC channel or mailinglist for these.

The nodejs interface (the one on 8088) seems to keep saying 'disconnected'. Is 
it still a work in progress or should I do something to connect it somehow?

Original issue reported on code.google.com by tim.st...@gmail.com on 12 Feb 2013 at 2:41

[GoogleCodeExporter]

Running server.js from the command line you should see something like this:
(btw, mtgox shouldn't be disconnecting, I suspect it's an issue on their side.)

$ node server.js
   info  - socket.io started
CONNECTED : https://socketio.mtgox.com:443/mtgox
server.js: ch_trades-amt: 119.09496629, ch_trades-price: 25.18999
server.js: ch_trades-amt: 9.42967015, ch_trades-price: 25.18999
DISCONNECTED : https://socketio.mtgox.com:443/mtgox
CONNECTED : https://socketio.mtgox.com:443/mtgox
server.js: 1min price: 25.18999, 1min volume: 128.52463644
server.js: 1min price: NaN, 1min volume: 0
server.js: ch_trades-amt: 51.6181, ch_trades-price: 25.18494
server.js: 1min price: 25.18494, 1min volume: 51.6181
server.js: ch_trades-amt: 21.4875, ch_trades-price: 25.18494
server.js: ch_trades-amt: 3.535, ch_trades-price: 25.18494

Also, the webpage wont connect to the ga-bitbot websocket when accessing the 
server through localhost (http://localhost:8088). You must either use the 
loopback address (127.0.0.1) or the IP address. It's this web socket connection 
which is generating the connected / disconnected status.

Original comment by brian.mo...@gmail.com on 13 Feb 2013 at 3:57

[GoogleCodeExporter]

I was using the (firewalled) external IP address, since I've got ga-bitbot 
running on a VPS. Still shows disconnected, whichever address I use...

Also, localhost is an alias for 127.0.0.1 (check you /etc/hosts), why would 
that make a difference?

Original comment by tim.st...@gmail.com on 13 Feb 2013 at 10:25

[GoogleCodeExporter]

I'm not sure why it would make a difference, the webserver still operates over 
localhost, it's the websocket connection that's failing. I'll have to look into 
the socket.io connections to verify they're setup correctly.

If your trying to access the web page on a remote server the only port you 
should need to have open on your remote firewall is 8088. If the firewall is 
already open then all I can think of is that it's interfering with the web 
socket connection somehow.

I ran a test yesterday on an AWS server with all ports open and I could access 
it no problem. I'll run another test tonight with only the 8088 port open and 
see what happens.

Original comment by brian.mo...@gmail.com on 15 Feb 2013 at 11:28

[GoogleCodeExporter]

PEBKAC, sorry. Didn't occur to me that it needs to contact 8088 from the 
browser, I had an Apache Proxy setup. Works now and is pretty awesome.

Original comment by tim.st...@gmail.com on 15 Feb 2013 at 12:16

[GoogleCodeExporter]

Original comment by brian.mo...@gmail.com on 6 Mar 2013 at 2:05

• Changed state: Invalid