aampohl
December 28, 2019, 4:50am
1
I've been having trouble getting the recent shiny server to work (using Ubuntu .deb installed with gdebi). I am getting "Not Founds" on situations where a directory with index.Rmd should be served by default. The regular app.R, etc shiny apps work fine. It also works fine being explicit with the URL and including "index.Rmd". But "directory_index on" (the default) doesn't seem to be doing its job entirely.
As a reprex, go get the recent rocker/shiny-verse docker image (which uses the same .deb I do). Run it and you'll see a "Not Found" in the lower right part of the Shiny welcome page, because that iframe sources a directory. Change the index.html to have that URL instead include "index.Rmd" as mentioned by Dirk here:
opened 12:13PM - 21 Apr 19 UTC
closed 04:49PM - 01 Apr 20 UTC
Hello! I tried to run shiny-verse container but it does not render demo RMarkdo… wn application:
.
Looks like the problem is in missing JS files, see 404 HTTP responses):
The docker image info and container logs are:
```
$ docker image ls rocker/shiny-verse:latest
REPOSITORY TAG IMAGE ID CREATED SIZE
rocker/shiny-verse latest 0052bf0992e2 23 hours ago 1.86GB
$ docker container run --rm -it -p 3838:3838 rocker/shiny-verse:latest
*** warning - no files are being watched ***
[2019-04-21T12:01:09.630] [INFO] shiny-server - Shiny Server v1.5.11.924 (Node.js v8.11.3)
[2019-04-21T12:01:09.636] [INFO] shiny-server - Using config file "/etc/shiny-server/shiny-server.conf"
[2019-04-21T12:01:09.796] [WARN] shiny-server - Running as root unnecessarily is a security risk! You could be running more securely as non-root.
[2019-04-21T12:01:09.805] [INFO] shiny-server - Starting listener on http://[::]:3838
[2019-04-21T12:01:13.470] [INFO] shiny-server - Created bookmark state directory: /var/lib/shiny-server/bookmarks
[2019-04-21T12:01:13.476] [INFO] shiny-server - Created user bookmark state directory: /var/lib/shiny-server/bookmarks/shiny
*** '/var/log/shiny-server//rmd-shiny-20190421-120113-39745.log' has been created ***
*** /var/log/shiny-server//rmd-shiny-20190421-120113-39745.log ***
Listening on http://127.0.0.1:39745
processing file: index.Rmd
output file: /tmp/RtmpclJleh/index.knit.md
Output created: /tmp/RtmpclJleh/file13770584f4.html
```
However, when I built shiny-verse image myself from source (https://github.com/rocker-org/shiny/blob/master/shiny-verse/Dockerfile) it works without problem.
and you'll see what you're supposed to. Is there some setting I'm missing or some basic thing?
Thanks.
cole
December 28, 2019, 11:52am
2
Is this a Shiny Rmd? What version of rmarkdown are you using? This sounds very much like a RMarkdown bug that was on CRAN for a bit (in 1.18 I think?), but the latest from CRAN resolves:
opened 09:41PM - 01 Dec 19 UTC
closed 03:12AM - 04 Dec 19 UTC
bug
[UPDATED: Please find comment below]
Hi all,
I would be very grateful if I… could receive some help with a 'Not Found' error that I and another user have encountered, only over the last days, when deploying Flexdashboard-Shiny apps to the shinyapps.io server. Would you please find the **initial issue [on the community](https://community.rstudio.com/t/not-found-error-when-deploying-to-shinyapps-io-whereas-app-deployed-well-hours-ago-and-still-does-locally/46029/2)**.
**The error may be reproduced** by deploying a Flexdashboard-Shiny (`runtime: shiny`) app such as [this one](https://jjallaire.shinyapps.io/shiny-ggplot2-brushing/) to the shinyapps.io server.
Since this error has emerged only over the last two days for myself, and I think it's the same for the other user who commented on my Community post, I've tried to spot any relevant, recent releases to CRAN. The RMarkdown package seems to have been updated these days, indeed with changes around Shiny (https://github.com/rstudio/rmarkdown/commit/d4d2a8fbc71c321baf55840e9967d438ab2f2c0a). I would be really grateful if someone could test this issue by deploying any Flexdashboard-Shiny app (e.g., from [the examples](https://rmarkdown.rstudio.com/flexdashboard/examples.html)) to the shinyapps.io server.
Cross-posting: https://github.com/rstudio/shiny/issues/2715. I'll take care of updating and closing all posts as soon as the issue has been resolved.
Thank you very much!
<!--
Please keep the below portion in your issue. Your issue will be closed if any of the boxes is not checked (i.e., replace `[ ]` by `[x]`). In certain (rare) cases, you may be exempted if you give a brief explanation (e.g., you are only making a suggestion for improvement). Thanks!
-->
---
By filing an issue to this repo, I promise that
- [x] I have fully read the issue guide at https://yihui.org/issue/.
- [x] I have provided the necessary information about my issue.
- If I'm asking a question, I have already asked it on Stack Overflow or RStudio Community, waited for at least 24 hours, and included a link to my question there.
- If I'm filing a bug report, I have included a minimal, self-contained, and reproducible example, and have also included `xfun::session_info('rmarkdown')`. I have upgraded all my packages to their latest versions (e.g., R, RStudio, and R packages), and also tried the development version: `remotes::install_github('rstudio/rmarkdown')`.
- If I have posted the same issue elsewhere, I have also mentioned it in this issue.
- [x] I have learned the Github Markdown syntax, and formatted my issue correctly.
I understand that my issue may be closed if I don't fulfill my promises.
Note that directory_index on has nothing to do with serving index.Rmd, etc. directory_index on allows users to "see" the list of applications available in a given folder by navigating to the folder URL. This is a fairly consistent paradigm with file servers, and is an analog that you may be familiar with from CRAN, for instance:
https://cran.rstudio.com/src/contrib/Archive/rmarkdown/
aampohl
December 28, 2019, 6:38pm
3
I upgraded it and yes that worked. Sorry to maybe throw you off then. index.Rmd files are now working as they should and directory_index works as it should. Thanks.
1 Like
system
January 18, 2020, 6:38pm
4
This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.