Skip to content

Troubleshooting SSL related issues in Posit products#

RStudio is now Posit!

Our professional products have been renamed to Posit Connect, Posit Workbench, Posit Package Manager, Posit Cloud, and Posit Academy so it’s easier for folks to understand that we support more than just R. Please review our Blog post/FAQ to answer commonly asked questions about the rebrand.

Posit Professional products (Posit Workbench [formerly RStudio Workbench], Posit Connect [formerly RStudio Connect], and Posit Package Manager [formerly RStudio Package Manager]) can be configured to use SSL Certificates.


This guide provides examples of a few common scenarios that you may encounter while configuring or using SSL certificates in Posit Professional products and how to troubleshoot them.

Configure SSL#

The configuration instructions are covered in a separate topic.

To review the configuration instructions, please select one of the following links for your product:

Scenario 1: SSL Certificates don't work when Publishing to Connect#


While publishing content from Workbench to an Connect instance with SSL configured, the user may encounter an error related to certificate not trusted.


In order to resolve this, you will have to register the certificate used by Connect in the Workbench server. The instructions depend on the flavor of Linux being used.

Scenario 2: Workbench and Connect are not able to download packages from Package Manager#


install.packages package isn't working correctly.

When the Package Manager server has an SSL certificate assigned to it, then the Linux OS for both Workbench and Connect needs to trust the certificate. If not, then the install.packages package does not work correctly.


This issue is similar to the issue described in Scenario 1. It can be resolved by following the Linux-flavor specific instructions to add SSL certificates to the machine.

Scenario 3: SSL Certificate not working with Local Launcher#


Error when launching sessions.

If you have configured local launcher in Workbench and are using SSL certificates, you might encounter an error while launching sessions.

The error will read like:

Console output
Error launching jobs:

"please verify your callback address setting for launcher.conf."


In order to resolve this issue, you need to update the Local launcher configuration so that the launcher uses the correct callback address of the Workbench that has an SSL certificate added to it.

Scenario 4: Troubleshooting SSL Issues with pins package#


Error when Shiny Apps are trying to access pins.

A common issue when using pins is when the user can successfully push pins to an Connect server and call the pins, but Shiny Apps that are trying to access the pin are failing.

The error will read like:

Console output
"Error in value[[3L]](cond) : Peer's Certificate issuer is not recognized."


A potential solution for this issue is to add the certificate that is used by the Connect server to the trusted store on the Connect server itself, given that it's local request.

If that doesn't work or if it isn't an option, then you can approach this issue from your R code instead. To approach this using your R code, execute the following setting before the pins package is used:

Console output
httr::set_config(config(ssl_verifypeer = FALSE, ssl_verifyhost = FALSE))

Didn't find a solution?#

If your scenario is not covered by this guide and you are still having trouble, please: