Dash Enterprise Administration
4.3.2
4.3.2
  • 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. Advanced Configuration

Sync license changes

PreviousTransfer Dash Enterprise to a new serverNextChange channels for an upgrade

Last updated 1 year ago

Was this helpful?

If Plotly support has made changes to your Dash Enterprise license, a sync is required for these changes to be reflected in your instance.

To sync the license for an internet-connected instance:

  1. Go to the Dash Enterprise Server Manager (available on port 8800 of your server’s IP or base domain).

  2. Select the gear icon > View License.

  3. Select Sync License.

To sync the license for a fully offline instance:

  1. Load the license:

replicatedctl license-load --airgap-package /<path>/bundle.airgap < /<path>/license.rli

where <path> is the path to the bundle and license files. For example:

replicatedctl license-load --airgap-package /home/ubuntu/bundle.airgap < /home/ubuntu/license.rli

  1. Restart Dash Enterprise. You can do this using the command line or the Dash Enterprise Server Manager.

    • From the command line: Run sudo replicatedctl app stop, wait for the stop to complete, and then run sudo replicatedctl app start.

    • From the Dash Enterprise Server Manager (available on port 8800 of your server’s IP or base domain): Select Stop Now, wait for the stop to complete, and then select Start Now.