Before you install
Dash Enterprise is a powerful data visualization platform designed to run on its own server or virtual machine. To support your needs, we offer different methods of installing the software, but the below requirements apply to all methods.
Open ports
The following open ports are required:
Port 443 (HTTPS): Required for creating, viewing, or administering Dash Apps.
Port 8800 (Server Manager UI, via HTTPS): Required for administrators to install, upgrade, and configure Dash Enterprise. You may restrict access to this port to administrators only.
The following ports are optional but recommended:
Port 80 (HTTP): All Dash Enterprise requests are made over HTTPS, so this port is not strictly required for full functionality. However, opening this port will allow Dash Enterprise to automatically redirect HTTP requests to use HTTPS; without this port, HTTP requests will simply fail.
Port 3022 (Dash app deployment via SSH): To support app deployment over SSH, Dash Deployment Server requires a port for SSH connections (default port 3022, configurable in Server Manager Settings). If you do not open a port for Dash app deployment via SSH, you will still be able to deploy Dash apps using HTTPS.
We do not recommend changing this to port 22, since you would need to disable SSH on the server.
Domain name requirements
Dash Enterprise needs one domain name and a corresponding DNS entry:
Dash Enterprise Domain Name: Required to use Dash Enterprise; users will visit this address to use Dash Enterprise (example:
dash.your-domain.com)Individual Dash apps will be available at https://dash.your-domain.com/appname
The DNS entries can be either CNAME or A records, but all must be fully qualified domain names. If using Dash Enterprise Single Server, the DNS entries for these domains should point to the single server’s IP address. If using a load balancer (see Load balancer configuration) or installing Dash Enterprise Kubernetes, the DNS entries should point to the load balancer IP.
Note - Domain names cannot contain "v2" in their name. This is a bug that will be resolved in a future release. For example,
dash-dev2.acme.comwould not be allowed.
TLS/SSL certificates
All access to Dash Enterprise is over HTTPS web connections secured using TLS/SSL, and Dash Enterprise will redirect all HTTP requests to HTTPS if the appropriate ports are opened. If necessary, Dash Enterprise will also generate its own self-signed certificates; however, using self-signed certificates will require your users to suppress security warnings in their web browsers and other software. To avoid this, we recommend obtaining TLS/SSL certificates issued by a certificate authority (CA).
If you are using a load balancer, it can be used to perform TLS/SSL termination. In this case, adding certificates is not required (see Load balancer configuration for more information).
Each domain name you configure requires its own certificate. There are two ways to achieve this:
1 - Multiple certificates: you can provide a certificate for each of these domain names (up to 3, depending on the features you enable); or
2 - Wildcard certificate: a single certificate for *.your-domain.com can cover all these domains, as long as they are only one level deep:
Any domain name of the form subdomain.your-domain.com will be covered (for example, plotly.your-domain.com, dash.your-domain.com)
Additional levels of subdomains will not be covered (for example, dash.yourdepartment.your-domain.com, plotly.test.your-domain.com)
A note on self-signed certificates
Both self-signed and certificates issued by certificate authorities (CAs) allow for secure encryption of the information sent to your Dash Enterprise server. The difference is that, when establishing an HTTPS connection, your web browser will check whether the connection is signed by a recognized CA and will raise a warning if the connection is untrusted (as when secured by a self-signed certificate).
In general, it is not a good idea to become accustomed to suppressing security warnings, since this increases the risk of falling prey to an unauthorized website’s impersonation attempt. However, if you are certain the certificate being offered belongs to your Dash Enterprise instance, you can ignore the warning. The safest way of ensuring that the self-signed certificate belongs to your Dash Enterprise instance is to distribute the certificate (.crt file) via a trusted connection to all intended users of the site.
Docker requirements for running Dash Enterprise
Dash Enterprise is compatible with Docker versions up to 22.X.X.
Here are some OS and Docker version combinations that are known to work well:
OS and Docker Repository Link | Docker Version |
20.10.21 | |
20.10.7 | |
20.10.21 | |
20.10.21 | |
18.03.1 | |
18.06.3 | |
19.03.15 | |
20.10.21 |
See also Docker storage driver requirements and considerations.
External service information
LDAP and SAML authentication
Dash Enterprise supports authentication using your company’s existing LDAP or SAML authentication system, as well as self-service or administrator-managed account creation modes. You can switch between authentication modes at will. Detailed instructions for authentication configuration are available in Configure basic settings.
When using LDAP, Dash Enterprise supports restricting login to a specified set of groups and sharing files with specified groups.
To use SAML, your SAML identity provider must add Dash Enterprise as a trusted service provider or relying party. Dash Enterprise supports restricting licensed user status to members of groups specified on the SAMP IdP, and any individual SAML user can be added as a Dash app collaborator after logging into Dash Enterprise once, which initializes their user account.
Last updated