Widgets are not displaying values

[joshmmo]

I installed dashing on an ec2 instance which is running ubuntu. Followed the getting started guide and managed to get dashing up but I am running into an issue.

The widgets are not updating according to the jobs. Even with the default sample.erb and sample.rb.

I can see valuation should be updating with a random number every 2 seconds, however, nothing happens.

I created a new dashboard and attempted to do a simple random number as well but same issue.

If the demo has the sample jobs it should also be updating as well no?
http://dashingdemo.herokuapp.com/sample

This is my dashboard I created:

home.erb
http://snipt.org/Ahfje5

current_visitors.rb:
http://snipt.org/Ahfjf2

I am running ruby 2.0.0p247

[pushmatrix]

Anything interesting popping up in the javascript console?

[joshmmo]

Yeah actually something does come up:

Timestamp: 9/25/2013 12:42:20 PM
Error: Firefox can't establish a connection to the server at http://stats.mysite.com:3030/events.
Source File: http://stats.mysite.com:3030/assets/application.js
Line: 15004

and

Timestamp: 9/25/2013 12:42:20 PM
Warning: Unknown property 'zoom'. Declaration dropped.
Source File: http://stats.mysite.com:3030/assets/application.css
Line: 686, Column: 6
Source Code:
zoom: 1; }

Any reason why /events does not work?

Same issues on the demo site as well. I tried FF/Chrome

[joshmmo]

Another thing I noticed, when I stop the server, the numbers for widgets will display.

[26/Sep/2013 17:27:07] "GET /events HTTP/1.1" 200 - 1423.9648
184.xxx.xxx.xxx - - [26/Sep/2013 17:27:07] "GET /events HTTP/1.1" 200 - 16.2585

[martinowen]

@joshmmo I'm seeing the same issue on a client's machine which is behind a HTTP proxy. Everything works for me in Firefox without a proxy, so I'm thinking the proxy is modifying the response in some way that Firefox doesn't like. Unfortunately it's difficult for me to debug as I don't have direct access to the client's machine (or proxy).

I'll let you know if I solve this as I'm working with them on it remotely.

[joekearney]

I've got this to work using webrick instead of thin. I'm running the server on a linux box, clients elsewhere. To do this:

rackup -p 3030 -s webrick

instead of

dashing start

-p for port, -s for server choice from {thin, puma, webrick, mongrel}, I've not tried the others.

I don't know why it doesn't work in thin, something to do with the eventing stuff. Note than when you kill the server all of the events get through to the browser.

[thomaspons]

Same issue here and my environement variable (i'm on windows) HTTP_PROXY is set ... Really Strange

[joshmmo]

I do not have a proxy setup so that is not the issue I am having. It is quite strange, I have two subdomains pointed to the same server. One subdomain works just fine and the other one gives me this issue.

I switched from an ec2 instance to a local server on my network. Still similar issue with multiple subdomains. I will try webrick instead of thin to see if this works for me.

[joshmmo]

webrick seemed to have fixed the issue