-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't load RStudio in Iframe (mixed-content) #4
Comments
Do you have |
Hi @mnazarov, yes but it didn't seem to help. I did do some tests directly on the rstudio container spawned by shinyproxy however and discovered that the redirect only happens when |
ok, but the above WWW_ROOT_PATH seems to be correct... |
As @mnazarov mentioned, it's important to use the correct rstudio docker image. As you can read in the readme, RStudio 4.0.0 and later requires at least ShinyProxy 2.5.0. Can you specify which ShinyProxy and RStudio version you are using? |
Dear All, I could confirm. With shinyproxy-rstudio-ide-demo/nginx/AWS ELB (elastic load balancer) I see the same issue when trying to launch newer version of Rstudio: openanalytics/shinyproxy-rstudio-ide-demo:2021.09.2_382__4.1.2:
However, the older version of Rstudio: openanalytics/shinyproxy-rstudio-ide-demo:1.2.1335__3.6.0 seems to be working just fine. In my setup shinyproxy is version 2.6.1 and DISABLE_AUTH set to true. |
AWS support confirmed that aws elb doesn’t alter requests coming from the target back to client, thus http is returned to https client and things break. Seems like to fix the issue the solution must be found for the target (container/nginx). |
this fixed the issue: |
I configured ShinyProxy with Rstudio as described in the example. My shinyproxy host is running under https but for some reason the iframe tries to reach the url using http (see error below)
Mixed Content: The page at 'https:///sp/app/rstudio' was loaded over HTTPS, but requested an insecure frame 'http:///sp/app_direct_i/rstudio/_/auth-sign-in?appUri=%2F'. This request has been blocked; the content must be served over HTTPS.
The strange thing is I also configured JupyterLab as described here and it works with no issue, which makes me doubt that the issue is in my nginx proxy
It seems to me it's caused by this redirect to /auth-sign-in which seems to be trying http
The text was updated successfully, but these errors were encountered: