Firefox and Google Chrome not working with Shiny?

2,218 views
Skip to first unread message

Ooi Wen Fong

unread,
Jun 7, 2013, 1:46:30 AM6/7/13
to shiny-...@googlegroups.com
Hi, 
 I am using Firefox 21.0 and Google Chrome 27.0.1453.110 m to open the Shiny examples.
 However, I see only the UI components such as buttons, slider, textbox. But I do not see any chart/graph display in the browser.

 What should I do?

Thanks

Wen Fong

Joe Cheng

unread,
Jun 7, 2013, 4:40:56 AM6/7/13
to shiny-...@googlegroups.com
Those should work fine. Do you see any errors in your browsers' JavaScript consoles?



Wen Fong

--
You received this message because you are subscribed to the Google Groups "Shiny - Web Framework for R" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shiny-discus...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
 
 

Ken B

unread,
Jun 7, 2013, 5:55:50 AM6/7/13
to shiny-...@googlegroups.com
Hi,

I get the same, on all my windows browsers (Chrome, FF, IE). I see the buttons, slider, textbox, but no output. When the page loads, the box colour changes from white to grey overlay.

I am no expert, but I had a look at the consoles.

In IE, when pressing F12, I see this error:
SCRIPT12030: WebSocket Error: Network Error 12030, The connection with the server was terminated abnormally

In FF: I get in the error consoles:
Timestamp: 07/06/2013 11:40:49
Error: The connection to ws://glimmer.rstudio.com/rstudio/faithful/__sockjs__/363/gfvu_yb4/websocket was interrupted while the page was loading.
Source File: http://cdn.sockjs.org/sockjs-0.3.min.js
Line: 27

Timestamp: 07/06/2013 11:46:54
Error: Uncaught asynchronous error: ReferenceError: aReason is not defined at
task@resource://app/modules/sessionstore/_SessionFile.jsm:214
TaskImpl_run@resource://gre/modules/Task.jsm:193
effort@resource://gre/modules/commonjs/sdk/core/promise.js:55
rejected@resource://gre/modules/commonjs/sdk/core/promise.js:118
then@resource://gre/modules/commonjs/sdk/core/promise.js:45
resolve@resource://gre/modules/commonjs/sdk/core/promise.js:143
rejected@resource://gre/modules/commonjs/sdk/core/promise.js:118
then@resource://gre/modules/commonjs/sdk/core/promise.js:45
resolve@resource://gre/modules/commonjs/sdk/core/promise.js:143
reject@resource://gre/modules/commonjs/sdk/core/promise.js:153
onmessage@resource://gre/modules/osfile/_PromiseWorker.jsm:137

Source File: resource://app/modules/sessionstore/_SessionFile.jsm
Line: 108

On chrome the console seems emtpy, but then again I'm no expert.

I'm behind a corporate firewall, which might also be a factor.

Let me know if you want me to test anything further, glad to help.

Rgds
Ken

Joe Cheng

unread,
Jun 7, 2013, 12:17:24 PM6/7/13
to shiny-...@googlegroups.com
Ken, that does sound like your corporate firewall is blocking websockets connections. They must be going out of their way to do that, because websockets run on the same port as regular HTTP requests. Is that something you can ask your IT people about? If they have a reason for blocking websockets I'd love to know why.

Ooi, are you also trying to connect to the examples on glimmer.rstudio.com, or are you trying to run them locally on your own R session?

Markus Naepflin

unread,
Jan 21, 2014, 11:38:48 AM1/21/14
to shiny-...@googlegroups.com
Hi there,
I got the same problem as described by Ooi Wen Fong. Buttons, slider are present and can be used, but there is no graph.
I tested it with two browsers and got following error messages:
 
- IE 9:
Script5009: "WebSocket" ist undefiniert
shiny.js, Zeile 453 Zeichen 9
 
which translates to:
Script5009: "WebSocket" ist undifined
shiny.js, row 453 character 9
 
- Chrome 32.0.1700.76 m:
WebSocket connection to 'ws://localhost:8100/' failed: Error during WebSocket handshake: Sent non-empty 'Sec-WebSocket-Protocol' header but no response is received.
 
 
Both browser can load the showcases on the RStudio Website without problem.
 
Any Ideas what could be the reason, or hints for our IT Departement?

 

Thanks  -  Markus

Joe Cheng

unread,
Jan 22, 2014, 10:58:27 AM1/22/14
to Markus Naepflin, shiny-...@googlegroups.com
Hi Markus,

IE8 and 9 are not supported by Shiny apps, unless they are served using Shiny Server. IE didn't get websocket support until IE10, and Shiny Server provides a workaround to support browsers that don't support websockets.

For the Chrome issue, can you try upgrading to a later version of Shiny? Just an install.packages("shiny") and restart of R should do it, if not please let us know. Thanks.


--

Markus Naepflin

unread,
Jan 23, 2014, 2:55:06 AM1/23/14
to shiny-...@googlegroups.com, Markus Naepflin
Hi Joe
 
Oh, I didn't realise, that a was using an older version of shiny. Now that I updated, everything works fine.
 
Thanks  -  Markus

Tim Phan

unread,
Jan 28, 2014, 11:43:43 PM1/28/14
to shiny-...@googlegroups.com
Hi Joe,

I've been stuck on this for a while too. Gray overlay, no output, looks like this

I've re-installed Shiny many times like you suggested, but no luck. I'm guessing it must have something to do with my localhost? I'm currently on my Mac laptop, but it works perfectly fine at my office PC.

Any suggestions would be great, you're awesome.

Tim

Tim Phan

unread,
Jan 29, 2014, 12:19:25 AM1/29/14
to shiny-...@googlegroups.com
PS, just discovered another thing. 

The gray overlay and lack of output happens in Google Chrome, but when I open up Safari or Firefox and reload "http://localhost:8100/" everything works out fine. Any idea to the reason for this?

Tim

Patrick Toche

unread,
Jan 29, 2014, 12:46:53 AM1/29/14
to shiny-...@googlegroups.com
and you have cleared the cache and/or uninstalled and re-installed chrome? and what OS are you using (version and all)?

Tim Phan

unread,
Jan 29, 2014, 1:04:10 AM1/29/14
to shiny-...@googlegroups.com
Yep, cleared the cache and re-installed Chrome. I'm using Mac OSX 10.7.5 and R 2.15.2

Jeff Allen

unread,
Jan 29, 2014, 1:35:17 PM1/29/14
to shiny-...@googlegroups.com
Tim,

Can you send us any messages printed to the console in Chrome when it disconnects?

Thanks.

Nick Benes

unread,
Feb 18, 2014, 3:40:19 PM2/18/14
to shiny-...@googlegroups.com
Tim,

You may want to update to R version 3.  I was having a similar problem with 2.15 and it looks like shiny is no longer supporting versions prior to 3. 
Reply all
Reply to author
Forward
0 new messages