Versions Compared

Old Version 15

changes.mady.by.user Gill Houghton

Saved on

compared with

New Version 16

changes.mady.by.user Gill Houghton

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

  1. Export the Chariot configuration through the Chariot Web UI from the left hand menu under System > Backup/Restore


  2. If configured for SSL, copy  NoteAny SSL/TLS certificates will not be included as part of this exportssl.jks keystore from <OLD_chariot_install_folder>/security directory
  3. Deploy the latest version of the AWS Chariot MQTT Server or Azure Chariot MQTT Server

  4. Stop the Chariot MQTT Server service on the existing instance of the Chariot MQTT Server
    For Chariot MQTT Server version 2.4.1 and newer 

    sudo systemctl stop chariot

    For Chariot MQTT Server versions prior to 2.4.1 

    sudo /etc/init.d/chariot stop


  5. If configuring SSL, copy ssl.jks keystore from Step 3 to <NEW_chariot_install_folder>/security

    Warning

    If you fail to do the copy BEFORE you start Chariot for the first time, the certs will not get picked up dynamically.


  6. Start the Chariot MQTT Server service on the new instance of the Chariot MQTT Server created in Step 23
    For Chariot MQTT Server version 2.4.1 and newer

    sudo systemctl start chariot

    For Chariot MQTT Server versions prior to 2.4.1

    sudo /etc/init.d/chariot start


  7. Make sure to reload any SSL/TLS certificates as they are not included in the exported configuration

    Restore the backed up config from Step 1 above to the new instance of the Chariot MQTT Server using the Chariot Web UI from the left hand menu under System > Backup/Restore

    Note



  8. Confirm clients can connect successfully to the new instance of the Chariot MQTT Server created in Step 2

  9. Stop and terminate/delete the old instance of the Chariot MQTT Server.