These instructions assume that your current Dash Enterprise instance is at least version 4.0.0. You must upgrade to 4.0.x before upgrading to 4.1.2; it is not possible to skip major versions when upgrading.
Browse to the Server Manager dashboard on port
8800 and click Stop Now
If you are using Dash Enterprise Kubernetes, you can use
replicatedctl app stop
Now, wait for app to stop.
To determine how much disk space your data directory is using, run the following command.
sudo du -sh /plotly
In this example, the output is
540M /plotly . The data directory is using 540 megabytes.
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/dockersudo 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.
Back up the Plotly data directory by creating a tar archive, and keep it somewhere safe.
sudo tar -czvf plotly_data_dir.tar.gz /plotly
When using Dash Enterprise Kubernetes, you will need to create two snapshots: one for your Redis database, and one for your Postgres database. This is because neither of them are saved inside
The process of creating a snapshot is described in the Using Snapshots & Backups section.
If your server can access the Internet, re-run the installation script:
curl -sSL https://get.plot.ly | sudo bash
If your server uses a proxy to access the Internet, see Configuring a proxy
If prompted for the server’s service IP address, press Enter to accept the default
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.
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 Microsoft’s documentation for more information and for instructions.