pplr_get_data() breaks: problem with curl::curl_fetch_memory's TOKEN

[AldoCompagnoni]

pplr_get_data() has recently stopped working. Upon download, the function throws the following error:

Error in curl::curl_fetch_memory(x$url$url, handle = x$url$handle) : schannel: next InitializeSecurityContext failed: SEC_E_INVALID_TOKEN (0x80090308) - The token supplied to the function is invalid

This code reproduces the error:

devtools::install_github('ropensci/popler') pplr_get_data( proj_metadata_key == 1 )

Regarding the session:

Session Info

```r R version 3.6.1 (2019-07-05) Platform: x86_64-w64-mingw32/x64 (64-bit) Running under: Windows 10 x64 (build 18362) Matrix products: default locale: [1] LC_COLLATE=English_United States.1252 [2] LC_CTYPE=English_United States.1252 [3] LC_MONETARY=English_United States.1252 [4] LC_NUMERIC=C [5] LC_TIME=English_United States.1252 attached base packages: [1] stats graphics grDevices utils datasets [6] methods base other attached packages: [1] popler_0.2.0 loaded via a namespace (and not attached): [1] Rcpp_1.0.2 pillar_1.4.2 compiler_3.6.1 [4] dbplyr_1.4.2 tools_3.6.1 digest_0.6.20 [7] jsonlite_1.6 evaluate_0.14 tibble_2.1.3 [10] gtable_0.3.0 pkgconfig_2.0.2 rlang_0.4.0 [13] DBI_1.0.0 rstudioapi_0.10 crul_0.8.4 [16] curl_4.0 xfun_0.9 dplyr_0.8.3 [19] stringr_1.4.0 knitr_1.24 triebeard_0.3.0 [22] grid_3.6.1 tidyselect_0.2.5 glue_1.3.1 [25] httpcode_0.2.0 R6_2.4.0 rmarkdown_1.15 [28] ggplot2_3.2.1 purrr_0.3.2 tidyr_0.8.3 [31] magrittr_1.5 urltools_1.7.3 scales_1.0.0 [34] htmltools_0.3.6 assertthat_0.2.1 colorspace_1.4-1 [37] stringi_1.4.3 lazyeval_0.2.2 munsell_0.5.0 [40] crayon_1.3.4 ```

I have tried to re-install old versions, and the current development version of the R package curl, but the error persists.

I have also checked that the online database is running correctly, and so are the web servers associated with the API locally (puma) and not (Caddy).

[AldoCompagnoni]

@sckott , any help on this will be very much appreciated!

[sckott]

Caddy was down - i just restarted it on the server

[AldoCompagnoni]

Thanks @Sckott!

This is embarrassing: I had killed and started caddy, so I had assumed it was running. There must be something I am doing wrong when I re-start caddy: at least now I know how to diagnose it.

I'll close the issue, and reopen it if, once the issue comes back, I am not able to debug it by myself.

[sckott]

when you're logged in run history | grep 443 and you'll see what I did

[AldoCompagnoni]

Thanks, the output does make sense!