Authenticating to Dash Enterprise with SSH

This documentation is for Dash Enterprise,
Plotly’s commercial platform for managing and improving
Dash applications in your organization.
View the docs or
request a trial.

In Plotly Enterprise 2.4.0 and above, you can deploy your apps using
either HTTPS or SSH. If you are deploying with HTTPS, then you do not
need to set up an SSH key. Thus, you can skip this tutorial and go
straight to
Initialize Dash Apps on Dash Enterprise.


If you are deploying with SSH then you need to add a SSH Key to the
Dash Enterprise. SSH Keys are used to authenticate your git
session with the server. Deploying with SSH takes a little bit more
time to set up but it allows you to deploy without typing in your
username and password each time. Continue below for instructions on
how to generate and add a SSH Key.

Why Deploy with SSH?

We recommend deploying with HTTPS for most of our users. However, there
are a few cases where deploying with SSH is advantageous:

  • If your Dash Enterprise is using a self-signed certificate,
    deploying with HTTPS
    requires some extra, challenging configuration.
    In these cases, it will be easier to configure deployment using SSH.
  • If your Dash Enterprise is configured with SAML, then the
    HTTPS method will not work.
  • If you are experiencing connectivity issues due to network latency, consider deploying with SSH instead; this method is often less susceptible to timeouts than HTTP, and so may provide a more reliable means of deploying your app.
    deploying with HTTP

Already Have an SSH Key?

If you already have an SSH key that you’ve used in other
services, you can use that key instead of generating a new one.
For instructions on how to add an existing SSH Key to Dash Enterprise,
scroll down to Copy and Add SSH Key.

Generate and Add an SSH Key

Which OS Are You Using?