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

Run preflight checks

PreviousSet up your Server ManagerNextConfigure basic settings

Last updated 2 years ago

Was this helpful?

These pre-installation checks are designed to ensure that your server meets the requirements to run Dash Enterprise smoothly. Once they have passed, click Continue.

Some check failures or warnings do not impede installation or use of Dash Enterprise (see next subsection). If any checks apart from those result in errors or warnings, consult before proceeding.

Preflight check failure: no route to host

Errors similar to dial tcp 10.0.20.51:9879: getsockopt: no route to host occasionally occur on Centos/RHEL systems and are typically a result of firewall restrictions on your server. To determine whether the firewall is the issue:

  • Open a terminal and run sudo systemctl stop firewalld

  • Reload the preflight checks page

If the above resolves the issue, disable firewalld (if possible) to continue. If disabling firewalld is not an option, add docker0 to the list of active zones, using the below commands as an example:

firewall-cmd --zone=trusted --add-interface=docker0
firewall-cmd --reload
Plotly support