Shiny App Deployment Error : purrr, curl and proxy errors

rstudio
rstudioconnect

#1

I tried to deploy a shinyapp, however the system prompt me an error which is the purrr packages, curl and proxy issue... I wanna access backend terminal sudo install it but dont know the user and password for beta.rstudioconnect.com, somebody shade me a light?

## Log Download
06/01 11:25:30.763
# Validating R library read / write permissions --------------------------------
06/01 11:25:30.792
# Validating packrat installation ----------------------------------------------
06/01 11:25:30.792
Installed packrat SHA is: a0b92cac860c2751e27f5432f49496e1241e04c5
06/01 11:25:30.792
Packaged packrat SHA is: a0b92cac860c2751e27f5432f49496e1241e04c5
06/01 11:25:30.793
Packrat is up-to-date.
06/01 11:25:30.794
R version: 3.4.0
06/01 11:25:30.794
packrat version: 0.4.9.2
06/01 11:25:30.794
# Validating packrat cache read / write permissions ----------------------------
06/01 11:25:30.981
Audited package hashes with local packrat installation.
06/01 11:25:30.986
# Installing required R packages with `packrat::restore()` ---------------------
06/01 11:25:31.155
Installing BH (1.66.0-1) ...
06/01 11:25:31.179
Using cached BH.
06/01 11:25:31.180
OK (symlinked cache)
06/01 11:25:31.180
Installing R6 (2.2.2) ...
06/01 11:25:31.308
Using cached R6.
06/01 11:25:31.309
OK (symlinked cache)
06/01 11:25:31.309
Installing Rcpp (0.12.17) ...
06/01 11:25:31.333
Using cached Rcpp.
06/01 11:25:31.333
OK (symlinked cache)
06/01 11:25:31.334
Installing assertthat (0.2.0) ...
06/01 11:25:31.354
Using cached assertthat.
06/01 11:25:31.355
OK (symlinked cache)
06/01 11:25:31.355
Installing backports (1.1.2) ...
06/01 11:25:31.378
Using cached backports.
06/01 11:25:31.379
OK (symlinked cache)
06/01 11:25:31.379
Installing bindr (0.1.1) ...
06/01 11:25:31.401
Using cached bindr.
06/01 11:25:31.402
OK (symlinked cache)
06/01 11:25:31.402
Installing crayon (1.3.4) ...
06/01 11:25:31.425
Using cached crayon.
06/01 11:25:31.426
OK (symlinked cache)
06/01 11:25:31.426
Installing digest (0.6.15) ...
06/01 11:25:31.449
Using cached digest.
06/01 11:25:31.450
OK (symlinked cache)
06/01 11:25:31.450
Installing glue (1.2.0) ...
06/01 11:25:31.473
Using cached glue.
06/01 11:25:31.474
OK (symlinked cache)
06/01 11:25:31.474
Installing jsonlite (1.5) ...
06/01 11:25:31.497
Using cached jsonlite.
06/01 11:25:31.498
OK (symlinked cache)
06/01 11:25:31.498
Installing magrittr (1.5) ...
06/01 11:25:31.519
Using cached magrittr.
06/01 11:25:31.520
OK (symlinked cache)
06/01 11:25:31.520
Installing mime (0.5) ...
06/01 11:25:31.542
Using cached mime.
06/01 11:25:31.543
OK (symlinked cache)
06/01 11:25:31.543
Installing packrat (0.4.9-2) ...
06/01 11:25:31.567
Using cached packrat.
06/01 11:25:31.567
OK (symlinked cache)
06/01 11:25:31.568
Installing pkgconfig (2.0.1) ...
06/01 11:25:31.589
Using cached pkgconfig.
06/01 11:25:31.590
OK (symlinked cache)
06/01 11:25:31.590
Installing plogr (0.2.0) ...
06/01 11:25:31.612
Using cached plogr.
06/01 11:25:31.613
OK (symlinked cache)
06/01 11:25:31.613
Installing rlang (0.2.0) ...
06/01 11:25:31.636
Using cached rlang.
06/01 11:25:31.637
OK (symlinked cache)
06/01 11:25:31.637
Installing sourcetools (0.1.7) ...
06/01 11:25:31.660
Using cached sourcetools.
06/01 11:25:31.661
OK (symlinked cache)
06/01 11:25:31.661
Installing utf8 (1.1.4) ...
06/01 11:25:31.683
Using cached utf8.
06/01 11:25:31.684
OK (symlinked cache)
06/01 11:25:31.684
Installing xtable (1.8-2) ...
06/01 11:25:31.706
Using cached xtable.
06/01 11:25:31.707
OK (symlinked cache)
06/01 11:25:31.707
Installing checkmate (1.8.5) ...
06/01 11:25:31.731
Using cached checkmate.
06/01 11:25:31.732
OK (symlinked cache)
06/01 11:25:31.732
Installing cli (1.0.0) ...
06/01 11:25:31.755
Using cached cli.
06/01 11:25:31.755
OK (symlinked cache)
06/01 11:25:31.756
Installing htmltools (0.3.6) ...
06/01 11:25:31.787
Using cached htmltools.
06/01 11:25:31.788
OK (symlinked cache)
06/01 11:25:31.788
Installing bindrcpp (0.2.2) ...
06/01 11:25:31.823
Using cached bindrcpp.
06/01 11:25:31.824
OK (symlinked cache)
06/01 11:25:31.824
Installing later (0.7.2) ...
06/01 11:25:31.858
Using cached later.
06/01 11:25:31.859
OK (symlinked cache)
06/01 11:25:31.859
Installing BBmisc (1.11) ...
06/01 11:25:31.882
Using cached BBmisc.
06/01 11:25:31.883
OK (symlinked cache)
06/01 11:25:31.883
Installing pillar (1.2.3) ...
06/01 11:25:31.908
Using cached pillar.
06/01 11:25:31.908
OK (symlinked cache)
06/01 11:25:31.909
Installing promises (1.0.1) ...
06/01 11:25:31.955
Using cached promises.
06/01 11:25:31.956
OK (symlinked cache)
06/01 11:25:31.956
Installing tibble (1.4.2) ...
06/01 11:25:31.980
Using cached tibble.
06/01 11:25:31.980
OK (symlinked cache)
06/01 11:25:31.981
Installing httpuv (1.4.3) ...
06/01 11:25:32.034
Using cached httpuv.
06/01 11:25:32.034
OK (symlinked cache)
06/01 11:25:32.035
Installing purrr (0.2.5) ...
06/01 11:25:32.168
curl: (6) Could not resolve host: package-proxy
06/01 11:25:32.179
curl: (6) Could not resolve host: package-proxy
06/01 11:25:32.190
curl: (6) Could not resolve host: package-proxy
06/01 11:25:32.190
Warning: unable to access index for repository http://package-proxy/src/contrib:
06/01 11:25:32.190
'curl' call had nonzero exit status
06/01 11:25:32.201
curl: (6) Could not resolve host: package-proxy
06/01 11:25:33.243
curl: (6) Could not resolve host: package-proxy
06/01 11:25:34.261
curl: (6) Could not resolve host: package-proxy
06/01 11:25:35.274
curl: (6) Could not resolve host: package-proxy
06/01 11:25:36.286
curl: (6) Could not resolve host: package-proxy
06/01 11:25:37.289
FAILED
06/01 11:25:37.297
Error in getSourceForPkgRecord(pkgRecord, srcDir(project), availablePackagesSource(repos = repos), : Failed to retrieve package sources for purrr 0.2.5 from CRAN (internet connectivity issue?)
06/01 11:25:37.297
06/01 11:25:37.297
Unable to fully restore the R packages associated with this deployment.
06/01 11:25:37.297
Please review the preceding messages to determine which package
06/01 11:25:37.297
encountered installation difficulty and the cause of the failure.
06/01 11:25:37.297
06/01 11:25:37.297
Some typical reasons for package installation failures:
06/01 11:25:37.297
* A system library needed by the R package is not installed.
06/01 11:25:37.297
Some of the most common package dependencies are cataloged at:
06/01 11:25:37.297
https://github.com/rstudio/shinyapps-package-dependencies
06/01 11:25:37.297
06/01 11:25:37.297
* The R package requires a newer version of R.
06/01 11:25:37.297
06/01 11:25:37.297
* The C/C++ compiler is outdated. This is often true for packages
06/01 11:25:37.297
needing C++11 features.
06/01 11:25:37.297
06/01 11:25:37.297
* The R package is Windows-only or otherwise unavailable for this
06/01 11:25:37.297
operating system.
06/01 11:25:37.297
06/01 11:25:37.297
* The package is housed in a private repository that requires
06/01 11:25:37.297
authentication to access. For more details on this, see:
06/01 11:25:37.297
http://docs.rstudio.com/connect/admin/process-management.html#private-packages
06/01 11:25:37.297
06/01 11:25:37.297
The package description and documentation will list system requirements
06/01 11:25:37.297
and restrictions.
06/01 11:25:37.297
06/01 11:25:37.297
Please contact your RStudio Connect administrator for further help
06/01 11:25:37.297
resolving this issue.
06/01 11:25:37.300
Warning message:
06/01 11:25:37.300
In packrat::restore(overwrite.dirty = TRUE, prompt = FALSE, restart = FALSE) :
06/01 11:25:37.300
The most recent snapshot was generated using R version 3.4.4

I try to refer to below answer but dont know the user and password to tune it. curl: (6) Could not resolve host: google.com; Name or service not known


#2

When deploying on Rstudio Connect, packrat is used to reproduce your local environment in the connect server, mainly R versions and packages version.

Reading the log, we see that packrat tries to install purrr from http://package-proxy/src/contrib. That means, your purrr 0.2.5 version tries to get download not from the CRAN but from this specifc http://package-proxy ur that it not reachable from the connect server.

You could try to install purrr again on your local environment from CRAN and check that your current repos options is set toward a reachable CRAN (getOption("repos") or packrat::repos_list())

See if this is working then. Thanks!


#3

It looks like you might be attempting to deploy from rstudio.cloud (the reference to package-proxy is what gives me that impression). If so, we are aware of this issue but do not have a solution at this time. You can download the project from rstudio.cloud and deploy to a Connect instance from your local machine as a work around.


#4

Oh! I was not aware of that!
what I said is not completely wrong but not relevant in this context then I think... :thinking: