Dash Enterprise Administration
4.3.1
4.3.1
  • Changelog
  • Installation
    • Capacity Planning
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
    • Dash Enterprise Kubernetes
      • Amazon Web Services resource prerequisites
      • Google Cloud Platform resource prerequisites
      • Microsoft Azure resource prerequisites
  • Configuration
    • Set up your Server Manager
    • Run preflight checks
    • Configure basic settings
    • Authentication settings
      • Built-in local authentication
      • LDAP authentication
      • SAML authentication
    • Dash Enterprise Kubernetes additional required configuration
    • Configure optional settings
    • Add SELinux permissions to mapped directories
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
      • Dash Enterprise Kubernetes
    • Load balancer configuration
    • Reverse proxy setup instructions
    • Docker storage driver requirements and considerations
    • Import an LDAPS certificate from Active Directory into Dash Enterprise
    • Transfer Dash Enterprise to a new server
    • Sync license changes
    • Change channels for an upgrade
    • Admin panel reference
    • Configure Dash Enterprise to use common SAML IdPs
      • Active Directory Federation Services (AD FS)
      • PingFederate
      • Okta
    • Configure Dash Enterprise to use common LDAP IdPs
      • Okta
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise Single Server
      • Dash Enterprise for Kubernetes
    • After the upgrade
  • Advanced Troubleshooting
    • Dash Enterprise Architecture and Internals
    • Navigating the System
    • Navigating the Support Bundle
    • Getting Help and Reporting Issues
    • Troubleshooting Specific Issues
Powered by GitBook
On this page

Was this helpful?

  1. Configuration

Configure basic settings

PreviousRun preflight checksNextAuthentication settings

Last updated 2 years ago

Was this helpful?

  1. Read and accept the Plotly End User License Agreement

  2. Specify the path to your Plotly Data Directory

    • Installation on a Cloud Provider: use the default /plotly

    • Installation on your Own Server: use the data directory created in ​

    • Fully Offline Installations: use the data directory created in ​

  3. (If using Dash Enterprise) Under Dash Deployment Server, check Enable Dash On Premise

    • Leave Dash Deployment SSH Port at its default value (3022) unless you are already using this port number for a different purpose

  4. Under Base Domain Name and SSL certificate, enter the base domain name you selected in and select a TLS/SSL certificate option:

    • Use the Server Manager certificate to use the same certificate that you installed while following ​

    • Automatically generate a self-signed certificate

    • Upload an existing certificate and key to use a separate CA-issued certificate

      • The certificate file must contain the full CA chain (including all intermediate certificates) in order to avoid errors when connecting to your On-Premise instance via a browser or the Plotly API libraries

  5. If you enabled Dash On Premise: repeat step 5, but use the Dash domain name you chose

Configuration: Set up your Server Manager
Domain name requirements
Create Plotly data directory
Installation using Plotly script