Dash Enterprise Administration
4.1.0
4.1.0
  • v4.1.0 Changelog
  • Installation
    • Before you install
    • Dash Enterprise Single Server
      • Installation on cloud provider
      • On-premise installation on own server
      • Fully offline installation
      • VMware Edition 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
    • Other options and customizations
    • Using Snapshots & Backups
    • Running and logging into Dash Enterprise
    • Next steps
  • Advanced Configuration
    • General troubleshooting and problem solving
    • 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
  • Upgrade
    • Prepare for the upgrade
    • Upgrade
      • Dash Enterprise only instance
      • Dash Enterprise and Chart Studio Enterprise instance
    • After the Upgrade
Powered by GitBook
On this page
  • Initial consideration
  • Port setup
  • Listener setup
  • Domain (DNS) setup

Was this helpful?

  1. Advanced Configuration

Load balancer configuration

These instructions assume you are using a Classic Elastic Load Balancer (ELB) on Amazon Web Services. To configure a different type of load balancer, please consult the documentation for your load balancer.

Initial consideration

If using Dash Enterprise Single Server behind a load balancer, the ELB will need to be configured to pass requests to the server.

Port setup

The following ports must be opened on the ELB and the ELB target instance:

  • 443 (HTTPS)

  • 80 (HTTP)

    • This port is optional, as all requests are made over HTTPS

    • Enabling port 80 will allow Dash Enterprise to automatically redirect requests made on HTTP to HTTPS

  • 8800 (Server Manager)

  • 3022 (SSH connections to Dash Enterprise)

    • You cannot use standard SSH port 22 for this unless you disable SSH on the server, which we do not recommend

Listener setup

Configure listeners on ports 443, 80, and 3022 to point to instance ports 443, 80, and 3022, respectively.

Domain (DNS) setup

Domain entries should be set as CNAMEs pointing to the ELB DNS Name. For example, if the ELB has a DNS name of test.us-east-1.elb.amazonaws.com, DNS entries should be added as follows:

dash.your-company.com CNAME for test.us-east-1.elb.amazonaws.com

Then specify the domains in the Server Manager Settings as usual:

  • Dash Deployment Server Domain: dash.your-company.com

PreviousGeneral troubleshooting and problem solvingNextReverse proxy setup instructions

Last updated 4 years ago

Was this helpful?