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
  • Stop the server manager
  • Back up your Plotly data directory.
  • Check the size of your data
  • Check available disk space
  • Back up your data directory
  • Upgrade Docker if it is older than version 17.05.0
  • SAML authentication with Microsoft Active Directory

Was this helpful?

  1. Upgrade

Prepare for the upgrade

Stop the server manager

Browse to the Server Manager dashboard on port 8800 and click Stop Now

Back up your Plotly data directory.

Check the size of your data

To determine how much disk space your data directory is using, run the following command.

sudo du -sh /plotly

Replace /plotly with the name of your data directory if you used a different name during installation.

The command may take some time depending on data size; one minute is typical.

In this example, the output is 540M /plotly . The data directory is using 540 megabytes.

Check available disk space

Make sure you have enough free space for the upgrade

  • Check the space in both the Docker data directory (/var/lib/docker by default) and the Plotly data directory (/plotly by default)

sudo df -h /var/lib/docker 
sudo df -h /plotly

The output should look similar to the following:

Filesystem         Size Used Avail Use% Mounted on
/dev/mapper/plotly   456G 44G 390G 10%  /

In this example, there is 390GB of space available -- enough space to hold a backup copy of the data directory during the upgrade process.

We recommend having at least 100GB available for the Docker data directory and at least 200GB available for the Plotly directory before proceeding.

Back up your data directory

Back up the Plotly data directory by creating a tar archive, and keep it somewhere safe.

tar -czvf plotly_data_dir.tar.gz /plotly

Upgrade Docker if it is older than version 17.05.0

If your server can access the Internet, re-run the installation script:

curl -sSL https://get.plot.ly | sudo bash
  • If prompted for the server’s service IP address, press Enter to accept the default

It is safe to run this Installation command on existing installations. It will only upgrade dependencies and won't delete any of your existing data.

For an airgapped installation, download the appropriate Docker package and any required dependencies to a storage device, then transfer the package to your server and install it with:

sudo rpm -ivh <package_name>.rpm

if you're on CentOS/RHEL/Fedora, or:

sudo dpkg --install <package_name>.deb

if you're on Ubuntu/Debian.

SAML authentication with Microsoft Active Directory

PreviousOktaNextUpgrade

Last updated 4 years ago

Was this helpful?

If your server uses a proxy to access the Internet, see

If you’re using SAML authentication with Microsoft Active Directory 2012, 2016, or 2019, you may need to activate strong authentication for .NET applications. See for more information and for instructions.

Microsoft’s documentation
Configuring a proxy