R Shiny at IQSS
  • Introduction
  • Getting started
    • Determining your resource requirements
    • Applying for an account
  • Deploying
    • Setup your environment
    • Deploying an example Shiny app
    • Bootstrapping a new Shiny app or migrating a pre-existing Shiny application
    • Developing locally with RStudio
    • Developing locally using Docker
    • Speeding up deployments with Packrat
  • Configuration
    • Setting up a custom domain for your Shiny app
    • Installing additional system-level packages
    • Limiting the number of R Threads
  • Best Practices
    • File storage
    • Using promises
    • Adding routes
  • Troubleshooting
    • Resolving Application Error screen
    • Viewing app logs
    • Viewing resource consumption
    • Configuring Shiny session auto-reconnect
    • Getting support
Powered by GitBook
On this page
  1. Troubleshooting

Resolving Application Error screen

PreviousTroubleshootingNextViewing app logs

Last updated 5 years ago

When trying to access your Shiny application, do you see the screen below?

If so, something is wrong with your application. The most common culprits are listed below in order of their likeliness:

  • You ran out of system memory. See

  • You're installing a package from GitHub rather than CRAN. See .

  • You're using packages.install() outside of init.R, in your R server function. See

  • A required R library has a system-level dependency that isn't articulated in your Aptfile. See

  • You're trying to install rJava without installing a JDK. See

How can you determine which of the above (or, if you're lucky - an entirely different problem) is responsible for your application crash? Read on!

Limiting the number of R Threads
Using Packrat
Using Packrat
Adding System Packages
Adding System Packages
An application crash