undefined blank page with firefox #117

Just an additional info:
I do not get the blank page when deployed on a server, i.e. the bug happens when using localhost URLs.

Some context:

• no authentication
• shinyproxy 2.1.0 in a docker
• ubuntu 16.04
• docker CE 18.09.1

application.yml

proxy:
  port: 8080
  authentication: none
  hide-navbar: true
  container-wait-time: 200000
  docker:
      internal-networking: true
  specs:
  - id: myapp
    display-name: myapp
    description: myapp
    container-volumes: ["/home/karl/shinyproxy/../:/home/docker/proj/"]
    container-image: myapp
    container-network: shinyproxy-net
logging:
  file:
    shinyproxy.log

Dockerfile:

RUN mkdir -p /opt/shinyproxy/
RUN wget https://www.shinyproxy.io/downloads/shinyproxy-2.1.0.jar -O /opt/shinyproxy/shinyproxy.jar
COPY application.yml /opt/shinyproxy/application.yml

WORKDIR /opt/shinyproxy/
CMD ["java", "-jar", "/opt/shinyproxy/shinyproxy.jar"]

The app is run using the entrypoint:

ENTRYPOINT ["R", "-e", "shiny::runApp('shiny', host = '0.0.0.0', port = 3838)"]

The dockers are run like this:

docker network create shinyproxy-net
docker run -d \
--name shinyproxy \
-v /var/run/docker.sock:/var/run/docker.sock \
--net shinyproxy-net \
-p 8080:8080 \
shinyproxy

Then:

• I open http://localhost:8080/ in firefox
• click on the myapp link
  then I get the blank page:

<body>undefined</body>

Hi kforner,

Experimenting the same issue from two days, can't find a solution... Did you succeed to fix it ?

Thanks a lot,

Clément

Hmm in my case I have an apache proxy on top of it, so I think I just redirected on the app url.

@kforner @Cala3len Did you succeed to fix it? Thank you.

Having the same error here with a similar situation. Did anyone manage to get a sense of what's going on?

Was a long time ago and i do not remember the details. But for me it was a matching issue between shiny-server, docker and host ports...

Hi all

I encountered this issue today and tried to investigate it. As reported above the error does not happen when using Chromium/Chrome. It also only seems to happen when using a container that takes a bit longer to startup. With the following container I can easily reproduce it:

  - id: zeppelin
    display-name: Apache Zeppelin
    container-image: apache/zeppelin:0.8.1
    port: 8080

More interesting, this only happens when you access ShinyProxy from the server host. It doesn't happen when you access it from a different PC/VM. And finally it doesn't happen with the Kuberntes backend. Unfortunately I don't find any solution for this problem, I hope I'll eventually find a solution, but for now I can at least reproduce it.

Same problem. But if you wait and reload it continues. Anyone has a fix?

Hi everyone

First of all: this issue should only be happening if you are using ShinyProxy with docker in combination with Firefox on the same host that ShinyProxy and docker are running on. This is an inconvenient problem, but it should not affect your production environments.

However, I again did some research on this issue and it seems to be a bug in Firefox. I found this bug report on bugzilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1238377 , which seems quite related. A workaround in the report is to set network.notify.changed to false in about:config. With this option disabled, everything works properly for me. When enabling the option again, the problem happens again.

I did some more testing and I can reproduce the problem without ShinyProxy (using a simple Flaks application). Therefore I created a bug report in the Firefox bug tracker: https://bugzilla.mozilla.org/show_bug.cgi?id=1720833 let's see whether they can solve it.

The bug is still present in Firefox, but versions 3.0.2 of ShinyProxy includes a workaround for this. This also improves the startup when a request fails for any other reason.