Skip to content
This repository has been archived by the owner on Mar 7, 2018. It is now read-only.

No widgets appearing on dashboard #394

Closed
philscott10 opened this issue Jul 8, 2014 · 2 comments
Closed

No widgets appearing on dashboard #394

philscott10 opened this issue Jul 8, 2014 · 2 comments

Comments

@philscott10
Copy link

I have installed dashing on a linux machine (running RHEL6) by following the instructions in the getting started section, but all I get is black screen with the text "Try this: curl -d '{ "auth_token": "YOUR_AUTH_TOKEN", "text": "Hey, Look what I can do!" }' \http://localhost:3030/widgets/welcome" appearing at the top.

The output from dashing start when attempting to load the dashboard is the following:

[root@tempname test_dash]# dashing start
Thin web server (v1.6.2 codename Doc Brown)
Maximum connections set to 1024
Listening on 0.0.0.0:3030, CTRL+C to stop
For the twitter widget to work, you need to put in your twitter API keys in the jobs/twitter.rb file.
127.0.0.1 - - [08/Jul/2014 11:43:45] "GET /sample HTTP/1.1" 200 2276 0.0085

I have tried various different suggestions from posts and web pages including:

  • Using 'webrick' and 'puma' instead of 'thin' #193
  • Using a different version of ruby (both 1.9.3 and 2.1.2) #208
  • Editing config.ru #382
  • Accessing the dashboard locally and remotely on a windows machine in both Chrome and Firefox (I know IE doesn't work so never bothered with that)

None of these work and I'm still unable to see any widgets on my dashboard or view any data in them. If I use the curl command mentioned on the dashboard it doesn't show any errors, but nothing changes on the dashboard.

Can anyone offer advice to explain why this might not be working or suggest any steps to debug it further?

@njalk
Copy link

njalk commented Aug 11, 2014

Same issue here, running on Ubuntu-server, tried Firefox and Chrome. No errors given

@philscott10
Copy link
Author

Turns out this was a problem with OpenSSL version compatibility. I cleared out my old installation of OpenSSL and installed a brand new one from scratch and then it worked perfectly for me.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants