Skip to main content
Version: 8.1

Installing and Upgrading Ignition

The installation process for Ignition is designed to be as simple as possible. You can find installers on our Downloads page: https://inductiveautomation.com/downloads/ignition/.

The Downloads page has the dedicated Installers (called "installer" for all major operating systems) and ZIP files. Both options install Ignition, but the installers are generally easier to use. Download an installer and head to the appropriate section below. For information on ZIP file installation instead, refer to the ZIP File Installations page.

Make sure your system meets our minimum system requirements (also found on our Downloads page).

New in 8.1.17
The installer now provides timestamped logs for installs and upgrades in the logs directory. Timestamped uninstall logs are stored in the root install directory.
tip

Learn how to verify that your installation of Ignition is genuine at the bottom of this page.

Software Bill of Materials

New in 8.1.34

A Software Bill of Materials in SPDX 2.2 (JSON) format is now included when installing Ignition. The SBOM can be found in the installation directory at SBOM.txt. Third Party Licenses and Copyright Notices can be found at Notice.txt, also located in the installation directory.

Install Ignition

  1. Download an installer from our Downloads page.
  2. Run the installer.
Inductive University

Installing Ignition on Windows

Watch the video

  1. Select the installation type and follow the steps in the installation wizard. The Typical option includes a selection of many popular modules. Additional modules can be added after the installation, so we will use the Typical option for now.

:::

Installer Settings Breakdown

In most cases you can use the default settings in the installer. This section describes what each setting does.

  • Default Installation Directories This determines the installation directory. You're free to pick the directory you wish. See the Ignition Default Installation Directories section below for the default paths.

  • Gateway Service Name (Windows Only) This field allows you to choose the service name of Ignition, as it appears in the operating system's service listing.

  • Installation Options Allows which modules are included in your base installation. Your choices are Typical and Custom. The Typical option will use a select list of commonly used modules. The Custom option allows you to install specific modules. In most installations the Standard option will suffice, but do note you can always add modules and remove modules after the installation process.

  • Start Ignition Now Once the installer finishes, you'll be provided with an option to start the Gateway immediately. In most cases this is the desired option. You would only opt out of this choice if you didn't want the Gateway to start once the installer finishes.

Once finished, a web browser will open, and start off the System Commissioning process.

  • Install As a Service (Linux and MacOS only) Allows you to install Ignition as a service, allowing you to manage certain actions via command line. It is recommended to opt into this setting. For Windows systems Ignition is installed as a service by default as it is a requirement for Ignition to run.
  1. After the installation wizard finishes, a web browser will open and start the commissioning process. At this point you'll need to select your edition.

  • Standard Edition - Unlimited edition of our flagship platform. Designed for commercial use.

  • Edge Edition - A lightweight edition of Ignition suited for edge-of-network installations.

  • Maker Edition - A free, limited edition of Ignition for personal, non-commercial projects.

  1. Follow the steps in the commissioning process to complete installation. The System Commissioning process is a series of steps that further configure your Gateway. This process begins after installation or upgrading. In addition, it can be re-triggered via a password reset with the Gateway Command-Line Utility.

    • New in 8.1.1
      Set the Gateway Network Port

      As of 8.1.1, commissioning can now set the Gateway Network port in addition to the HTTP and HTTPS port.

      Clean installs of Ignition will check the default ports for their availability. If no ports are available, the Gateway will iterate that port number until one is found that is available. These ports can be modified during the commissioning process.

      Existing or upgraded Gateways will not search for available ports, and will result in a faulted Gateway.

      note

      By default, Linux will not allow you to run on port 1024 and below. If you need to run on one of these ports, such as port 80, you can add the CAP_NET_BIND_SERVICE capability to your systemd service configuration override file.

    • Activate License (Maker Edition Only) When installing Maker Edition, you'll be asked to provide a License Key (an 8 digit string) and an Activation Token (a considerably longer string). Both of these can be acquired for free from your Inductive Automation account: https://account.inductiveautomation.com/.

    • Create a User This step asks you to create an initial user. This user will have full access to Ignition, although you're free to modify this user later. You'll need this user account to make changes to Ignition at all, so make sure you remember these credentials. Otherwise you'll need to perform a password reset: see the Gateway Command-Line Utility page.

    • HTTP Configuration Allows you to specify the ports Ignition uses. By default, HTTP is 8088, and HTTPS is 8043.

Once you finish the commissioning process, your service will start.

Ignition Default Installation Directories

The default directories for each operating system are listed below.

Windows
C:\Program Files\Inductive Automation\Ignition
MacOS
/usr/local/ignition
Linux
/usr/local/bin/ignition

MacOS and Linux Installation Directory

New in 8.1.10

Mac and Linux installations contain a ignition.sh file and ignition-util.sh file, which both contain some configuration parameters for the installation. Modifying these files is not advised, unless directed to by a member of our support team. Instead, an ignition.shconf file, which is also located in the installation directory, should be used instead. Additionally, during installation on Mac and Linux, the installer will create a sudoer file at installationDirectory/etc/sudoers.d/99-<serviceName>, with the service name being Ignition-Gateway by default. This ensures the Gateway can be restarted without an interactive login. In most cases, the sudoer file does not need to be modified or maintained. However, more information can be found in the ignition-util.sh file in the installation directory.

Quick Start Configuration

New in 8.1.0

Once the installation process has finished, you'll be redirected to the Gateway Webpage. From there you'll be asked to opt into the Quick Start configuration, which makes several configuration changes to the system. Quick Start can only be enabled upon a new installation.

The following changes are made once Quick Start is enabled:

  • Creates an internal SQLite database connection.
  • Configures a device connection to a Programmable Device Simulator instance, and adds Tags from the simulator into a Tag provider.
  • Configures an internal alarm journal.
  • Creates a sample project.

Start or Stop Ignition

After installing with the Installer, Ignition will have a service representing it on the operating system. By default Ignition will start when the system starts, but you can manually start and stop the system with the following terminal commands:

Windows
## The examples below assume "Ignition" is the service named used during installation 
## (which also happens to be the default service name).
## You may need to modify the examples below using your system's service name.

net start Ignition
net stop Ignition
Mac
/usr/local/ignition/ignition.sh start
/usr/local/ignition/ignition.sh stop
/usr/local/ignition/ignition.sh restart
Linux
## The examples below use the default installation directory

/usr/local/bin/ignition/ignition.sh start
/usr/local/bin/ignition/ignition.sh stop
/usr/local/bin/ignition/ignition.sh restart

Upgrade Ignition

Upgrading Ignition is as easy as running the installer. When you run the installer from the same directory as a previous install, our installers are able to detect that Ignition is already installed. If Ignition is already installed, the installer will ask if you would like to proceed with the upgrade. A wizard takes you through the upgrade in a similar workflow as installation workflow.

Before completing the upgrade process, it is strongly advised to take a Gateway backup of your system first.

Ignition installers can be used to upgrade any edition of Ignition (i.e., Edge, Maker, or Standard) with the exception of ARM as that will require a ZIP installer for upgrading.

Linux Installer

Older versions of the Linux installer would place files across multiple different directories. Running an 8.0.14+ installer will move all those files to the specified installation directory, and symbolic link folders from the original directory will be created.

JDBC Drivers and Upgrading

Sometimes new versions of Ignition will incorporate new JDBC drivers, which are used to connect to SQL databases. When upgrading Ignition, the JDBC drivers will not be upgraded. The reason being, is that you should only need to change the JDBC driver if you upgrade your database. See the JDBC Drivers and Translators page for more details.

During the upgrade process, the Gateway will have to restart, so make sure to account for downtime when upgrading.

When you upgrade Ignition, you'll also be given the option to update any additional modules you currently have installed, including Third-Party modules. On the Select Modules screen, there is a tab for the modules included in your version of Ignition, and a tab for Additional Modules you may be using. Under the Action column, you can choose to upgrade or remove the module or leave it unchanged.

Updating License for an Upgrade

If you are updating from one major version to the next (i.e, upgrading from version 8.0.# to version 8.1.#) , you will need an updated license. You can do this before upgrading so there is no unlicensed time after the upgrade.

  1. Let us know. You can reach Inductive Automation by phone at (800) 266-7798. Some Major upgrades include new modules or have modified the functionality of pre-existing modules. If your license needs to be updated, call us and we can guide you through it. If you are updating from one version to the next, or from 7.0.0 all the way to the latest version, we can talk you though what is different and what new functionality is available. See the New in this Version page for more specifics about what was updated in the various versions.

    note

    If your license is covered by a support plan, you have Upgrade Protection which automatically keeps your platform and module versions up to date in our system. Refreshing your license on your Gateway will synchronize the license on your server with the updated license on our activation servers.

  2. Reload your license. Once your license is updated in our system, go to your Config section of the Gateway webpage, and click System > Licensing. Click on the Update License icon . For for a detailed guide on reloading a license, see updating a License on this page. If you are coming from an older version, the Gateway may look different. Don't worry, all this functionality is still there, but you may have to un-activate then re-activate instead if the Update License button is missing.

Upgrading a Redundant Pair

There are a few extra things to consider when upgrading a redundant pair of Gateways. When performing the upgrade locally, we recommend upgrading the Master first. This allows the Backup to take over when the Master is down for an upgrade, and the Master can resume operations when it comes back online. At this point the Backup can be upgraded without interruption. The same considerations mentioned above should also be applied to the redundant pair, but you only need a Gateway Backup file from the Master Ignition Gateway.

If the upgrade will be performed remotely using the Enterprise Administration Module, then the Backup Gateway should be upgraded first. This allows the EAM controller to manually tell clients/sessions to communicate with the newly upgraded Backup Gateway, even though the Master will be a different version, allowing time to upgrade the Master.

Depending on what version you are upgrading, you may have to choose between a few different upgrade method options to determine what will work best for your needs. If upgrading version 8.1.0-8.1.16, following the recommended process above will still successfully upgrade your system, but you'll need to manually resume Master control and take down the Backup. Based on how you resume your Master control, you may have duplicated data from the slight overlap of having both Gateways up or experience downtime when taking the Backup down before bringing the Master back up. Alternatively, you can use the following procedure to upgrade without disrupting your redundancy setup:

  1. Navigate to Status > System > Redundancy on your Master Gateway.
  2. Select Force Failover to set your Backup as your active Gateway.
  3. Navigate to Config > System > Redundancy on your Master Gateway.
  4. Adjust the Startup Connection Allowance setting to a large number. This will allow the Master to sit in the undecided state and not become active after being upgraded. Note the original value so you can reset it at the end of this process.

  1. Upgrade and start your Master Gateway.
  2. Wait for the Master to fully initialize and become ready to take back over.
  3. Shut down your Backup Gateway.
  4. Navigate to Config > System > Redundancy on your Master Gateway.
  5. Change the Mode setting to Independent.
  6. Change the Startup Connection Allowance setting to 0.
  7. Select Save Changes.
  8. Select Confirm.
  9. Now, change the Mode setting back to Master.
  10. Select Save Changes.
  11. Select Confirm.
  12. Upgrade your Backup Gateway.
  13. After the upgrade is complete, verify your Backup Gateway is connected and your redundancy is active.
  14. Navigate to Config > System > Redundancy on your Master Gateway.
  15. Return the Startup Connection Allowance setting to the original value.

Reset the Password

To reset the main password for the user with full privileges, use the Gateway Command-line Utility (gwcmd) utility. The 'gwcmd' utility triggers system commissioning, and prompts the user to reset the username and password for the main user (with full privileges) after the Gateway restarts. Linux and Mac OS platforms also use the 'gwcmd' utility for password reset. For more information, see the Gateway Command-line Utility - gwcmd page.

Uninstall Ignition

note

Uninstalling Ignition will remove any projects or Gateway level configurations you made. If you wish to preserve anything, make sure to take a Gateway backup first.

To uninstall Ignition, run the uninstaller file. This file can be found in the main Ignition installation directory, for example:

Windows
C:\Program Files\Inductive Automation\Ignition\Uninstall.exe
Mac
/usr/local/ignition/Uninstall.app
Linux
/usr/local/bin/ignition/Uninstall.run

Verify that Ignition Software is Genuine

Code signing is applied to installers to help the OS prevent the installer from being run if it has been tampered with. Notarization is an additional step on macOS that works with Apple’s systems to validate that the software has undergone their malicious code scanning.

Expected Certificate:

Name of signer: Inductive Automation, LLC

CN = DigiCert Trusted G4 Code Signing RSA4096 SHA384 2021 CA1

View verification of the digital signature on Ignition’s installer on Windows in the User Account Control popup when running the installer. It can also be viewed in the Digital Signatures section of the file Properties dialog.

  1. Right-click on the installer and select Properties.
  2. Under the Digital Signatures tab, select the signature from the Signature list and click Details.

  1. If the text "This digital signature is OK" appears under the General tab, the installer is genuine and has not been manipulated.

Verify the Download is Authentic by Hash Comparison

The Ignition automated build process writes a precalculated fingerprint (hash) to the download site allowing users to verify the authenticity of the download file. On the Downloads page, click sha-256 to view the hash for your selected installer file. You may also copy this hash to your clipboard for comparison.

A SHA256 hash of the downloaded installer package can be compared to the values on the website with terminal commands such as:

PowerShell
Get-FileHash path\to\installer
macOS/Linux
sha256sum /path/to/installer

Verify an Ignition Module Download is Authentic - Advanced

Ignition modules are collections of files and resources that are loaded and run by the Ignition Platform. Inductive Automation publishes a number of modules and third-party authors can also create modules through the Ignition Module SDK. In order to help verify file integrity of these modules, code signing is applied to ensure that the contained files and resources within the module package have not been tampered with.

Verification of a given Ignition module’s code signatures is handled automatically by the platform. The following manual verification steps (requires openssl) are listed below to provide a fuller understanding of the mechanisms at play:

  1. Extract the .modl file as a zip file into a working directory.
  2. Observe the contained certificates.p7b file which is a PKCS#7 package containing the certificate chain used for generating the signatures for each of the files within the .modl package.
  3. Observe the contained signatures.properties file. Each line contains a path to a file within the .modl package and a base64-encoded signature for the file.
  4. Extract the public key `signingPublicKey.pem from the certificates.p7b file with the following steps:
    • openssl pkcs7 -outform PEM -in certificates.p7b -print_certs > certificates.cer
    • openssl x509 -pubkey -noout -in certificates.cer > signingPublicKey.pem
  5. Decode the base64 content for a given file (from signatures.properties) into a signature file, e.g. signature.sign.
  6. Verify the signature of the file with the following:
    • openssl dgst -sha256 -verify signingPublicKey.pem -signature signature.sign <file from .modl>
  7. Observe a Verified OK message indicating that the signature from signatures.properties for the respective file is correct.